From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] base.bbclass: show layer's branches/revisions in the banner info
Date: Tue, 28 Jun 2011 18:01:00 -0700 [thread overview]
Message-ID: <4E0A794C.5060303@gmail.com> (raw)
In-Reply-To: <201106281207.23516.paul.eggleton@linux.intel.com>
On 06/28/2011 04:07 AM, Paul Eggleton wrote:
> On Tuesday 28 June 2011 07:45:09 Koen Kooi wrote:
>> So it works as expected, but the output is a bit confusing. I have a few
>> (conflicting) suggestions:
>>
>> 1) replace _BRANCH and _REVISION with ' branch' and ' revision', e.g.:
>>
>> meta-archos branch = "master"
>> meta-archos revision = "413933fb5f62574e38a9a1e38905ba6e9c1be4ad"
>>
>> 2) for the extra layers put branch and revision on a single line:
>>
>> meta-archos = "master/413933fb5f62574e38a9a1e38905ba6e9c1be4ad"
>
> I'd go with option 2 over 1, personally - the list gets rather long on
> something like Angstrom, better to keep it short.
I would say to do it uniformly and treat oe-core as one of layers too
when emitting this info
next prev parent reply other threads:[~2011-06-29 1:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 5:37 [PATCH 0/1] base.bbclass: show layer's branches/revisions in the banner info Dexuan Cui
2011-06-28 5:37 ` [PATCH 1/1] " Dexuan Cui
2011-06-28 6:45 ` Koen Kooi
2011-06-28 11:07 ` Paul Eggleton
2011-06-29 1:01 ` Khem Raj [this message]
2011-06-29 16:14 ` Cui, Dexuan
2011-06-29 16:19 ` Koen Kooi
2011-06-29 16:44 ` Cui, Dexuan
2011-06-29 18:32 ` Khem Raj
2011-06-29 21:16 ` Koen Kooi
2011-06-28 14:27 ` Mark Hatle
2011-06-28 14:52 ` Cui, Dexuan
2011-06-28 15:10 ` Koen Kooi
2011-06-28 15:21 ` Cui, Dexuan
2011-06-28 15:24 ` Phil Blundell
2011-06-28 15:33 ` Mark Hatle
2011-06-28 15:45 ` Cui, Dexuan
2011-06-28 15:51 ` Koen Kooi
2011-06-28 15:13 ` Koen Kooi
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=4E0A794C.5060303@gmail.com \
--to=raj.khem@gmail.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 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.