From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] linux-libc-headers: updated to 3.4.3
Date: Wed, 18 Jul 2012 14:23:49 +0100 [thread overview]
Message-ID: <1342617829.513.3.camel@ted> (raw)
In-Reply-To: <CADkTA4OkYB6ZsA81mz1YUrYeukVjrtSTph8b5mJ9jiomPibMKg@mail.gmail.com>
On Wed, 2012-07-18 at 09:03 -0400, Bruce Ashfield wrote:
> On Wed, Jul 18, 2012 at 7:30 AM, Marinescu, Bogdan A
> <bogdan.a.marinescu@intel.com> wrote:
> > On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >> Why is recipe renamed
> >
> > Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?
>
> No one replied to my other question (or at least no one replied that I
> noticed), about
> why we even bothered to bump it to 3.4.3 ...
>
> I have the same elements in that question .. but from a different angle.
I think Khem's question is a little vague and I'm not sure how I'd
answer that.
As for policy of updating the kernel headers against stable releases, it
can't hurt and we needed to bump PV or PR anyway as Martin mentioned so
that was the main reason I took the patch.
I think there could be a perception issue if we don't update, on the
other hand it could be considered unnecessary churn. So I think in
future this will be on a case by case basis. If there was a header fix
in the stable series (which is conceivable), we would want to take that
for example.
Cheers,
Richard
next prev parent reply other threads:[~2012-07-18 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 13:02 [PATCH] linux-libc-headers: updated to 3.4.3 Bogdan Marinescu
2012-07-17 15:58 ` Saul Wold
2012-07-17 16:54 ` Khem Raj
2012-07-18 11:30 ` Marinescu, Bogdan A
2012-07-18 13:03 ` Bruce Ashfield
2012-07-18 13:17 ` Marinescu, Bogdan A
2012-07-18 13:23 ` Bruce Ashfield
2012-07-18 13:50 ` Richard Purdie
2012-07-18 13:52 ` Marinescu, Bogdan A
2012-07-18 13:23 ` Richard Purdie [this message]
2012-07-18 13:27 ` 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=1342617829.513.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox