Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: deduce git revision from mtn revision
Date: Thu, 11 Jun 2009 01:02:42 +0200	[thread overview]
Message-ID: <200906110102.42993.zecke@selfish.org> (raw)
In-Reply-To: <h0ol24$79k$1@ger.gmane.org>

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,



  reply	other threads:[~2009-06-11  1:12 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 [this message]
2009-06-10 11:55 ` Michael Smith
2009-06-10 12:33 ` Tom Rini
2009-06-10 15:58   ` Rolf Leggewie

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=200906110102.42993.zecke@selfish.org \
    --to=zecke@selfish.org \
    --cc=openembedded-devel@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