[oe] [PATCH] metadata_scm.bbclass: get the metadata revision for current HEAD

[Martin Jansa]

On Wed, Nov 03, 2010 at 04:55:52PM -0700, Chris Larson wrote:
> On Wed, Nov 3, 2010 at 3:40 PM, Khem Raj <raj.khem at gmail.com> wrote:
> 
> > Currently we report wrong revision when we build from branches not based
> > on master because we only fetch the HEAD value which is remote master
> > This patch makes it to report the HEAD of whatever branch one has
> > checked out.
> >
> 
> This doesn't make sense.  The HEAD ref always points to the current checked
> out commit or branch, it is *not* specific to master.

No it does make sense, because it fixes my <unknown> METADATA_REVISION :).

Acked-by: Martin Jansa <Martin.Jansa at gmail.com>

in my R/W checkout I have it right even before patch

bitbake at jama ~/oe $ git show-ref HEAD
b3246d96069fd11caee42ec6ebcbf6dca2d62449 refs/remotes/origin/HEAD

OE om-gta02 at shr ~/oe $ git remote -v
jama    /OE/dev/ (fetch)
jama    /OE/dev/ (push)
....
origin  git at git.openembedded.org:openembedded (fetch)
origin  git at git.openembedded.org:openembedded (push)


but in my "work" checkout, where I have this R/W used as origin
bitbake at jama ~/dev $ git show-ref HEAD -> nothing

OE om-gta02 at shr ~/dev $ git remote -v
gitorious git at gitorious.org:~jama/angstrom/jama-shr-experimental.git (fetch)
gitorious git at gitorious.org:~jama/angstrom/jama-shr-experimental.git (push)
....
origin  /OE/oe/ (fetch)
origin  /OE/oe/ (push)

Regards,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com