All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Poky <poky@lists.pokylinux.org>, Chris Larson <clarson@kergoth.com>
Subject: Re: PR and .bbappend
Date: Wed, 02 Feb 2011 09:40:57 -0800	[thread overview]
Message-ID: <4D499729.5010809@linux.intel.com> (raw)
In-Reply-To: <4D49758C.30109@windriver.com>

On 02/02/2011 07:17 AM, Mark Hatle wrote:
> On 2/2/11 9:13 AM, Chris Larson wrote:
>> On Wed, Feb 2, 2011 at 8:03 AM, Gary Thomas<gary@mlbassoc.com>  wrote:
>>> Should .bbappend files have a PR in them?  If so, must it
>>> match the one in the main .bb file?
>>
>> All metadata in a .bbappend is essentially concatenated to the recipe.
>>   If you define PR in the .bbappend, it will override the one in the
>> recipe, which is unlikely what you want, as that loses information.
>> The better route is to do something like PR .= ".1" in the .bbappend,
>> and bump that when changing the bbappend file.
>
> I was going to suggest the same thing.  A good approach is to append a value to
> the existing PR.  (I suggest this get added as a best practice in the
> documentation on bbappend...  I'm not sure who the correct person is to point
> this out to though.)

That would be Scott R, on CC.

>
> --Mark
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


      reply	other threads:[~2011-02-02 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 15:03 PR and .bbappend Gary Thomas
2011-02-02 15:13 ` Chris Larson
2011-02-02 15:17   ` Mark Hatle
2011-02-02 17:40     ` Darren Hart [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=4D499729.5010809@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=clarson@kergoth.com \
    --cc=mark.hatle@windriver.com \
    --cc=poky@lists.pokylinux.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.