From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches,
discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Add 3.7 version of linux-libc-headers
Date: Tue, 18 Dec 2012 17:32:33 +0000 [thread overview]
Message-ID: <1355851953.18874.45.camel@ted> (raw)
In-Reply-To: <CADkTA4OAKuK6Sk0=vSnr6P+M8_svdZ2VNEbH18HZNbWt_LpzuQ@mail.gmail.com>
On Tue, 2012-12-18 at 08:56 -0500, Bruce Ashfield wrote:
> On Tue, Dec 18, 2012 at 8:41 AM, Marcin Juszkiewicz
> <marcin.juszkiewicz@linaro.org> wrote:
> W dniu 18.12.2012 14:32, Bruce Ashfield pisze:
> > On Tue, Dec 18, 2012 at 6:07 AM, Richard Purdie On Tue,
> 2012-12-11
> > If we bring this in, I'd prefer to completely drop the 3.4
> kernel
> > headers, since having just one recipe in the tree make
> sense, and it
> > won't tempt us to start having a trail of one libc-header
> per kernel
> > version (since there's always a layer somewhere that's using
> a given
> > version).
>
> > What about a middle ground ? I can pull this into my tree,
> since I'm
> > doing some 3.8 and 3.4-stable work at the moment, I'll
> remove the 3.4
> > kernel headers and then submit it again as part of my queue
> with some
> > extra tests run ?
>
>
> I am fine with it.
>
> Thanks, I'll pull this in if Richard agrees.
>
Sounds like a plan to me.
Cheers,
Richard
next prev parent reply other threads:[~2012-12-18 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 10:12 Add 3.7 version of linux-libc-headers Marcin Juszkiewicz
2012-12-11 10:12 ` [PATCH] linux-libc-headers: add 3.7 version Marcin Juszkiewicz
2012-12-11 10:52 ` Add 3.7 version of linux-libc-headers Bruce Ashfield
2012-12-18 11:07 ` Richard Purdie
2012-12-18 13:32 ` Bruce Ashfield
2012-12-18 13:41 ` Marcin Juszkiewicz
2012-12-18 13:56 ` Bruce Ashfield
2012-12-18 17:32 ` Richard Purdie [this message]
2013-01-03 21:14 ` Bruce Ashfield
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=1355851953.18874.45.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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.