Openembedded Core Discussions
 help / color / mirror / Atom feed
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:50:16 +0100	[thread overview]
Message-ID: <1342619416.513.7.camel@ted> (raw)
In-Reply-To: <CADkTA4NTBME99-JMBy1+22iwqV7nxpsB=CSsLNuT8wDKgQY-eA@mail.gmail.com>

On Wed, 2012-07-18 at 09:23 -0400, Bruce Ashfield wrote:
> On Wed, Jul 18, 2012 at 9:17 AM, Marinescu, Bogdan A
> <bogdan.a.marinescu@intel.com> wrote:
> > On Wed, Jul 18, 2012 at 4:03 PM, Bruce Ashfield
> > <bruce.ashfield@gmail.com> 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 ...
> >
> > Quite simply, I'm the owner of the recipe and I'm supposed to upgrade
> > it when a new version appears :)
> 
> I must have missed that .. because I'd disagree with both counts.
> 
>  - libc-headers does not need to be upgraded with every korg stable update
>  - it is coupled to the kernel, and I've done it in the past, and had planned to
>    leave it a 3.4.

Bogdan: This is probably one of the cases we shouldn't automatically
update just based on the output of the version checking scripts. We
should only change the point release version here if there is a change
to the kernel headers that we need.

As for the recipe owner, this one may be best owned by Bruce but I'm
open minded on that.


Cheers,

Richard




  reply	other threads:[~2012-07-18 14:01 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 [this message]
2012-07-18 13:52             ` Marinescu, Bogdan A
2012-07-18 13:23       ` Richard Purdie
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=1342619416.513.7.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