From: akuster808 <akuster808@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [for-krogoth] Backport for libc != glibc
Date: Mon, 20 Jun 2016 20:10:38 -0700 [thread overview]
Message-ID: <5768B02E.3070502@gmail.com> (raw)
In-Reply-To: <CAP9ODKquFwEALn2SAMa-wM6M-9gFQ_KZFMoks_26UYgk-Smr6A@mail.gmail.com>
On 06/20/2016 09:08 AM, Otavio Salvador wrote:
> On Mon, Jun 20, 2016 at 1:04 PM, Khem Raj <raj.khem@gmail.com> wrote:
> ...
>>> Could those be reviewed and queued for the next backport?
>>
>> They look fine for backport to krogoth. Please submit pull requests
>
> Armin can easily pick them; I gave the OE-Core hashes.
Ok got them. running test builds.
- armin
>
prev parent reply other threads:[~2016-06-21 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 13:27 [for-krogoth] Backport for libc != glibc Otavio Salvador
2016-06-20 16:04 ` Khem Raj
2016-06-20 16:08 ` Otavio Salvador
2016-06-21 3:10 ` akuster808 [this message]
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=5768B02E.3070502@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox