From: Johannes Sixt <j.sixt@viscovery.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: git@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Q: how can i find the upstream merge point of a commit?
Date: Wed, 08 Jun 2011 12:32:19 +0200 [thread overview]
Message-ID: <4DEF4FB3.1020400@viscovery.net> (raw)
In-Reply-To: <20110608093648.GA19038@elte.hu>
Am 6/8/2011 11:36, schrieb Ingo Molnar:
> So for example when was 189d3c4a94 merged upstream?
>
> The proper Git answer would be:
>
> $ git describe --contains 189d3c4a94
> next-20080501~97
>
> But the next-20080501 tag is useless, and i don't have linux-next as
> HEAD, it's only a remote.
> ...
> But ... it would be much nicer if i could make 'git describe
> --contains' work better.
$ git describe --contains --match 'v2.*' 189d3c4a94
-- Hannes
next prev parent reply other threads:[~2011-06-08 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 9:36 Q: how can i find the upstream merge point of a commit? Ingo Molnar
2011-06-08 10:32 ` Johannes Sixt [this message]
2011-06-08 10:34 ` Stephen Rothwell
2011-06-08 10:40 ` Peter Zijlstra
2011-06-08 11:29 ` Stephen Rothwell
2011-06-08 11:51 ` Peter Zijlstra
2011-06-08 12:52 ` Ingo Molnar
2011-06-08 13:49 ` Sverre Rabbelier
2011-06-08 14:27 ` Ingo Molnar
2011-06-08 15:23 ` Nguyen Thai Ngoc Duy
2011-06-14 9:56 ` Johan Herland
2011-06-14 17:12 ` Jeff King
2011-06-14 23:45 ` Johan Herland
2011-06-15 23:00 ` Jeff King
2011-06-15 23:53 ` Junio C Hamano
2011-06-16 0:48 ` Jeff King
2011-06-16 11:33 ` Jakub Narebski
2011-06-08 15:01 ` Junio C Hamano
2011-06-08 15:18 ` Ingo Molnar
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=4DEF4FB3.1020400@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=a.p.zijlstra@chello.nl \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).