All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Gary Thomas <gary@mlbassoc.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] Rename 'BRANCH' variable to 'SRCBRANCH' for clearness
Date: Thu, 17 Sep 2015 15:06:46 +0100	[thread overview]
Message-ID: <1442498806.26666.212.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKqAQiGTZ5vbQjcpYbywAto6caG9Vcvbx4KQbYeQnUY2JQ@mail.gmail.com>

On Thu, 2015-09-17 at 10:33 -0300, Otavio Salvador wrote:
> On Thu, Sep 17, 2015 at 10:30 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> > On 2015-09-17 07:21, Otavio Salvador wrote:
> >>
> >> The 'BRANCH' variable name has no explicit relation with the
> >> SRC_URI. Using 'SRCBRANCH' makes it more obvious and easier to
> >> identify.
> >>
> >> This patch makes the use consistent across the metadata.
> >>
> >> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> >
> >
> > These should be separated into one for glibc and another for mmc.
> > Also, the subject line needs to mention the recipe name based on
> > the commit guidelines.
> 
> I can split it but it does not make much sense for this specific case,
> IMO. This is a global change and so it provides an easier view of
> affected recipes for such a change. If it, supposedly, introduces a
> regression it is easier to revert it.

I don't think it needs to be split, I would like "glibc/mmc-utils:" at
the start of the subject line so we give the casual reader some idea
what the scope of the patch is though. In this case I'll just add that
before merging.

Cheers,

Richard



  reply	other threads:[~2015-09-17 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 13:21 [PATCH v2] Rename 'BRANCH' variable to 'SRCBRANCH' for clearness Otavio Salvador
2015-09-17 13:30 ` Gary Thomas
2015-09-17 13:33   ` Otavio Salvador
2015-09-17 14:06     ` Richard Purdie [this message]
2015-09-17 13:54 ` Khem Raj
2015-09-17 13:57   ` Otavio Salvador

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=1442498806.26666.212.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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.