Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 1/1] base.bbclass: show layer's branches/revisions in the banner info
Date: Tue, 28 Jun 2011 12:07:23 +0100	[thread overview]
Message-ID: <201106281207.23516.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <3819C41B-FF96-45FD-8265-8EFC9F73E771@dominion.thruhere.net>

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.
 
> 3) Move the revision info down, e..g
> 
> OE Build Configuration:
> BB_VERSION                  = "1.13.1"
> TARGET_ARCH                 = "arm"
> TARGET_OS                   = "linux-gnueabi"
> MACHINE                     = "beagleboard"
> DISTRO                      = "angstrom"
> DISTRO_VERSION              = "v2011.06-core"
> TARGET_FPU                  = "hard"
> METADATA_BRANCH             = "master"
> METADATA_REVISION           = "364ca0d2d0399c8cc6d3b3fc28308e1e14673544"
> meta-angstrom_BRANCH        = "master"
> meta-angstrom_REVISION      = "c19c342c62416752117c2dce4696840bc864f647"
> 
> etc.
> 
> What do you think about that?

Sounds good to me.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-06-28 11:11 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 [this message]
2011-06-29  1:01       ` Khem Raj
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=201106281207.23516.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --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