From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>,
"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>,
"Zanussi, Tom" <tom.zanussi@intel.com>
Subject: Using yocto/standard by default
Date: Tue, 13 Dec 2011 15:46:59 -0800 [thread overview]
Message-ID: <4EE7E3F3.8010003@linux.intel.com> (raw)
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?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next reply other threads:[~2011-12-13 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 23:46 Darren Hart [this message]
2011-12-14 5:27 ` Using yocto/standard by default Bruce Ashfield
2011-12-14 5:48 ` Darren Hart
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=4EE7E3F3.8010003@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=Bruce.Ashfield@windriver.com \
--cc=tom.zanussi@intel.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.