From: "Burton, Ross" <ross.burton@intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] Update libusb1 from 1.0.19 to 1.0.20
Date: Thu, 29 Oct 2015 19:02:41 +0000 [thread overview]
Message-ID: <CAJTo0LazGKCMy=_Sf3UjNPvKm0vDC2bfOL-sFNDcQ7a+10q_Aw@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKrj3XrhrUBjp7VssdqWbeMvKNm_iJSSQY0L7h-S7DmyLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
On 29 October 2015 at 12:37, Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:
> Due the memory leak fixes, I think we could consider the backport for
> 2.0.1 after it proves stable in master for some time.
>
Standard practise would be to cherry-pick the leak fixes, unless you can
convince the jethro stable maintainer (whoever that ends up being) that
nothing will break with an upgrade.
Ross
[-- Attachment #2: Type: text/html, Size: 831 bytes --]
next prev parent reply other threads:[~2015-10-29 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 14:36 [PATCH 1/1] Update libusb1 from 1.0.19 to 1.0.20 Jens Rehsack
2015-10-29 11:47 ` Jens Rehsack
2015-10-29 12:27 ` Paul Eggleton
2015-10-29 12:37 ` Otavio Salvador
2015-10-29 19:02 ` Burton, Ross [this message]
2015-10-29 19:03 ` Burton, Ross
2015-11-06 10:36 ` Burton, Ross
2015-11-07 10:36 ` Jens Rehsack
2015-11-07 23:31 ` Burton, Ross
2015-11-10 9:14 ` Jens Rehsack
2015-11-10 13:14 ` Burton, Ross
2015-11-13 9:53 ` Burton, Ross
2015-11-13 12:18 ` Jens Rehsack
2015-11-13 12:20 ` Burton, Ross
2015-11-13 12:25 ` Jens Rehsack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJTo0LazGKCMy=_Sf3UjNPvKm0vDC2bfOL-sFNDcQ7a+10q_Aw@mail.gmail.com' \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=paul.eggleton@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.