deduce git revision from mtn revision

deduce git revision from mtn revision

[Rolf Leggewie]

Hi,

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?

Regards

Rolf

Re: deduce git revision from mtn revision

[Holger Freyther]

On Wednesday 10 June 2009 07:21:37 Rolf Leggewie wrote:
> Hi,
>
> 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?

Indirectly... use git log by date...

z.

Re: deduce git revision from mtn revision

[Rolf Leggewie]

Holger, thank you for your comment.

Holger Freyther wrote:
> Indirectly... use git log by date...

Two questions

1) how do I actually do that? "git help log" did not know.
2) will that help if I only know the mtn rev id and not its date?

Re: deduce git revision from mtn revision

[Holger Freyther]

On Wednesday 10 June 2009 17:55:47 Rolf Leggewie wrote:
> Holger, thank you for your comment.
>
> Holger Freyther wrote:
> > Indirectly... use git log by date...
>
> Two questions
>
> 1) how do I actually do that? "git help log" did not know.
> 2) will that help if I only know the mtn rev id and not its date?

well, you can use mtn to get the date based on the revision and you can use 
git log --since= /--after...

z,

Re: deduce git revision from mtn revision

[Michael Smith]

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@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@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

Re: deduce git revision from mtn revision

[Tom Rini]

On Wed, Jun 10, 2009 at 02:21:37PM +0900, Rolf Leggewie wrote:

> Hi,
>
> 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?

I used mtn to find the whole commit, copy the commit message info and
then search for that commit message in git.

-- 
Tom Rini

Re: deduce git revision from mtn revision

[Rolf Leggewie]

Tom Rini wrote:
> I used mtn to find the whole commit, copy the commit message info and
> then search for that commit message in git.

I guess that is the only way that will consistently work.

Maybe we could prepare and store a list somewhere.