All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Smith, Elliot" <elliot.smith@intel.com>
Cc: "Belen Barros Pena \(Intel\)" <belen.barros.pena@linux.intel.com>,
	"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Patch prefixes
Date: Mon, 24 Aug 2015 10:59:25 +0100	[thread overview]
Message-ID: <1440410365.12105.317.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+1hgUi5-0H6afgg+y6n6DAJL9r_iwKbJYfVdTHvyph-AKBUEg@mail.gmail.com>

On Mon, 2015-08-24 at 09:44 +0100, Smith, Elliot wrote:
> Thanks for this information, but I just want to be 100% clear on this
> as I am new to the project. I've asked a question below.
>
> On 20 August 2015 at 11:26, Damian, Alexandru
> <alexandru.damian@intel.com> wrote:
>         In the "poky:" tree, we need to use:
> >
>         # bitbake: toaster: descriptive patch name
>
> So in my branches on poky-contrib, is it necessary for me to use
> "bitbake: toaster:" as a prefix for all my commits?

What you use in poky-contrib isn't particularly important. What matters
is when the patches come for merging on bitbake-devel, they state the
area they touch (often toaster:) but not "bitbake:" since in the bitbake
repo that is somewhat pointless. When these merge back to poky, the
bitbake prefix is automatically added.

Cheers,

Richard




      reply	other threads:[~2015-08-24  9:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 10:21 Patch prefixes Belen Barros Pena (Intel)
2015-08-20 10:26 ` Damian, Alexandru
2015-08-24  8:44   ` Smith, Elliot
2015-08-24  9:59     ` Richard Purdie [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=1440410365.12105.317.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=belen.barros.pena@linux.intel.com \
    --cc=elliot.smith@intel.com \
    --cc=toaster@yoctoproject.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.