From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Tom Zanussi <tom.zanussi@intel.com>
Cc: openembedded-core@lists.openembedded.org, scott.a.garman@intel.com
Subject: Re: [PATCH 0/1] [denzil] linux-yocto: make validate_branches handle non BSP branches
Date: Wed, 22 Aug 2012 01:48:47 -0400 [thread overview]
Message-ID: <503472BF.5000306@windriver.com> (raw)
In-Reply-To: <1345613248.17535.1.camel@trz-ThinkPad-T420>
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
On 12-08-22 1:27 AM, Tom Zanussi wrote:
> On Mon, 2012-08-13 at 13:10 -0400, Bruce Ashfield wrote:
>> Scott,
>>
>> Here's a fix for validate_branches that comes from a pending master
>> change that I've been running for 3 weeks, and one that TomZ has tested
>> in his yocto BSP work on denzil.
>>
>> It fixes some BSP use cases that involve setting a specific SRCREV
>> on a base branch, so that a BSP branch that doesn't yet exist can
>> be created off of that known base. Previously only an existing BSP
>> branch could have it's SRCREV restricted.
>>
>
> Hi Scott,
>
> I don't see this in denzil - do you have it queued for the next pull
> request, or did it get missed?
I was wondering the same thing, in particular, since I just made a minor
tweak to this in master (which I'll send out tomorrow). The attached
patch should also be merged to denzil.
Bruce
>
> Tom
>
>> cc: Tom Zanussi<tom.zanussi@intel.com>
>>
>> Cheers,
>>
>> Bruce
>>
>> The following changes since commit 73cdebf60df225ee10f2eb215935be3b61e1b831:
>>
>> documentation/dev-manual/dev-manual-kernel-appendix.xml: Add note about conflict (2012-06-29 15:54:26 +0100)
>>
>> are available in the git repository at:
>> git://git.pokylinux.org/poky-contrib zedd/kernel-denzil
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-denzil
>>
>> Bruce Ashfield (1):
>> linux-yocto: allow do_validate_branches to handle all branches
>>
>> meta/classes/kernel-yocto.bbclass | 119 +++++++++++++++++++++++++------------
>> 1 files changed, 80 insertions(+), 39 deletions(-)
>>
>
>
[-- Attachment #2: 0001-kernel-yocto-set-master-branch-to-a-defined-SRCREV.patch --]
[-- Type: application/mbox, Size: 1628 bytes --]
next prev parent reply other threads:[~2012-08-22 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 17:10 [PATCH 0/1] [denzil] linux-yocto: make validate_branches handle non BSP branches Bruce Ashfield
2012-08-13 17:10 ` [PATCH 1/1] linux-yocto: allow do_validate_branches to handle all branches Bruce Ashfield
2012-08-22 5:27 ` [PATCH 0/1] [denzil] linux-yocto: make validate_branches handle non BSP branches Tom Zanussi
2012-08-22 5:48 ` Bruce Ashfield [this message]
2012-08-23 19:18 ` Tom Zanussi
2012-08-23 19:21 ` Bruce Ashfield
2012-08-24 8:08 ` Scott Garman
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=503472BF.5000306@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@intel.com \
--cc=tom.zanussi@intel.com \
/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