[oe] deduce git revision from mtn revision

Michael Smith msmith at cbnco.com
Wed Jun 10 11:55:23 UTC 2009


On Wed, 10 Jun 2009, Rolf Leggewie wrote:

> is there any way to know which git revision corresponds to mtn commit
> 53dccbcb3344fa9a96f7f2c544d3dfec1b100fca?  I guess googling for the revision
> and then using git log can eventually yield that info. Anything simpler and
> more straight-forward?

It ended up in a log message by chance:

git log --grep=53dccbcb3344fa9a96f7f2c544d3dfec1b100fca
commit d7d081c7ea40ea61365ca51b892cf7af8a802298
Merge: 06c89ee c3e353c
Author: Henning Heinold <heinold at inf.fu-berlin.de>
Date:   Wed May 7 20:07:39 2008 +0000

    merge of '53dccbcb3344fa9a96f7f2c544d3dfec1b100fca'
         and 'fea7dedc0a856ea56969779e97c888a16ffc63de'

I guess it's probably this one:

commit 06c89ee737a0f595efee34ea1a250c190825db7c
Author: Rolf Leggewie <oe-devel at rolf.leggewie.biz>
Date:   Wed May 7 19:27:30 2008 +0000

    pointercal: backpush pointercal files for qemuarm and htcuniversal 
from poky
.  Closes 3742 (it at least masks the superficial problem).

Mike




More information about the Openembedded-devel mailing list