From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: deduce git revision from mtn revision
Date: Thu, 11 Jun 2009 00:58:56 +0900 [thread overview]
Message-ID: <h0ol82$79k$2@ger.gmane.org> (raw)
In-Reply-To: <20090610123349.GT26065@smtp.west.cox.net>
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.
prev parent reply other threads:[~2009-06-10 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 5:21 deduce git revision from mtn revision Rolf Leggewie
2009-06-10 4:27 ` Holger Freyther
2009-06-10 15:55 ` Rolf Leggewie
2009-06-10 23:02 ` Holger Freyther
2009-06-10 11:55 ` Michael Smith
2009-06-10 12:33 ` Tom Rini
2009-06-10 15:58 ` Rolf Leggewie [this message]
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='h0ol82$79k$2@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.