From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] linux-yocto: branch manipulation changes
Date: Tue, 17 May 2011 11:26:10 -0700 [thread overview]
Message-ID: <4DD2BDC2.4000401@linux.intel.com> (raw)
In-Reply-To: <cover.1305564106.git.bruce.ashfield@windriver.com>
On 05/16/2011 09:52 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Recently a few alternate workflow/use cases have been
> looked at recently. While they aren't existing cases, or
> ones that were previously supported, they are reasonable
> so I've tweaked the tools and processing to support them.
>
> The first change is to allow AUTOREV processing to skip
> branch validation (since it doesn't make sense). The second
> change allows a repository with only a single BSP branch
> and a meta directory to be present .. and the tools can
> reconstruct what they need to validate and build the
> kernel.
>
> Tested against the new use cases, and existing ones, all
> performed properly.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: zedd/kernel
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
> Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (1):
> linux-yocto: detect and avoid branch revision checking for AUTOREV
>
> meta/classes/kernel-yocto.bbclass | 7 +++++++
> .../kern-tools/kern-tools-native_git.bb | 2 +-
> 2 files changed, 8 insertions(+), 1 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into oe-core and poky
Thanks
Sau!
prev parent reply other threads:[~2011-05-17 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 16:52 [PATCH 0/1] linux-yocto: branch manipulation changes Bruce Ashfield
2011-05-16 16:52 ` [PATCH 1/1] linux-yocto: detect and avoid branch revision checking for AUTOREV Bruce Ashfield
2011-05-17 18:26 ` Saul Wold [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=4DD2BDC2.4000401@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox