From: Gary Thomas <gary@mlbassoc.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra][PATCH] More changes for git fetchers
Date: Wed, 11 Dec 2013 04:14:50 -0700 [thread overview]
Message-ID: <52A8492A.4070108@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKo4UA4owwNLwtpksoGZVvNFfF16ZtjK+nq89d4WL6CVfg@mail.gmail.com>
On 2013-12-11 03:14, Otavio Salvador wrote:
> Hello,
>
> On Tue, Dec 10, 2013 at 2:50 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> Recipes now need to explicitly mention the branch used for git repositories.
>> These changes reflect this, allowing for the branch to be overridden by
>> .bbappend files
>>
>> Signed-off-by: Gary Thomas <gary@mlbassoc.com>
>
> I opted to apply Philip changes (in its last revision which included
> SRCBRANCH) as it were split in several commits and with a specific
> commit log for each, which is more in line on how we do the commit
> logs usually.
>
> Please check if anything is missing at your side and let me know.
>
These are all fine, thanks.
n.b. I'm not so sure about the multiple commits since they are all
for the same reason. Splitting them up would make it harder for
someone in the future to make sure they found all the related changes
if they wanted to. No worries.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-12-11 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 16:50 [meta-fsl-arm-extra][PATCH] More changes for git fetchers Gary Thomas
2013-12-11 10:14 ` Otavio Salvador
2013-12-11 11:14 ` Gary Thomas [this message]
2013-12-11 11:29 ` 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=52A8492A.4070108@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@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.