From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Using yocto/standard by default
Date: Tue, 13 Dec 2011 21:48:45 -0800 [thread overview]
Message-ID: <4EE838BD.5040605@linux.intel.com> (raw)
In-Reply-To: <4EE833C1.9010705@windriver.com>
On 12/13/2011 09:27 PM, Bruce Ashfield wrote:
> On 11-12-13 6:46 PM, Darren Hart wrote:
>> We hit another lock-step SRCREV bug earlier on the FRI2 BSP. This was
>> due mostly to my pushing the efi changes to meta-intel too early - but,
>> it highlights a maintenance step that I believe could be eliminated for
>> most boards.
>>
>> We have a yocto/standard/fri2 branch, but it doesn't contain any
>> additional changes over yocto/standard/base. If we were to make
>> yocto/standard/base the default for KBRANCH, shouldn't we be able to
>> eliminate all the BSP branches that are identical to
>> yocto/standard/base? This would significantly reduce the number of
>> SRCREV updates that are required and likely reduce the number of
>> Autobuilder failures we experience as a result. Seems like it would also
>> help make the git tree easier to deal with.
>>
>> Any opinions here?
>
> It's a valid config, and something that works now. So there's no
> reason to not use it. New branches can be created IF a board really
> does need to merge conflicting patches. The emgd stuff was a problem
> and required branches, but if we have nothing like that, squashing the
> branches is a nice simplification.
>
Hrm maybe I missed that in the fri2 branches. It does need emgd, so I'll
double check that.
> Cheers,
>
> Bruce
>
>>
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2011-12-14 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 23:46 Using yocto/standard by default Darren Hart
2011-12-14 5:27 ` Bruce Ashfield
2011-12-14 5:48 ` 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=4EE838BD.5040605@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=yocto@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.