From: Jeff King <peff@peff.net>
To: Paul Gardiner <osronline@glidos.net>
Cc: Avery Pennarun <apenwarr@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: How to find where a branch was taken from.
Date: Sat, 22 Mar 2008 12:41:37 -0400 [thread overview]
Message-ID: <20080322164136.GA7611@coredump.intra.peff.net> (raw)
In-Reply-To: <47E4F7A0.6060702@glidos.net>
On Sat, Mar 22, 2008 at 12:12:16PM +0000, Paul Gardiner wrote:
> Yes, that's exactly what I need too. I need to produce it
> programatically. I notice gitk displays, for each commit,
> the branches that include it. If I knew a command for
> deriving that, I could iterate through HEAD, HEAD~1, HEAD~2...
> until I see a remote branch.
How about:
git name-rev --refs='refs/remotes/*' $COMMIT
?
-Peff
next prev parent reply other threads:[~2008-03-22 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 9:05 How to find where a branch was taken from Paul Gardiner
2008-03-21 9:13 ` Junio C Hamano
2008-03-21 9:15 ` Junio C Hamano
2008-03-21 17:39 ` Avery Pennarun
2008-03-21 18:32 ` Charles Bailey
2008-03-21 18:48 ` Avery Pennarun
2008-03-21 20:03 ` Dmitry Potapov
2008-03-21 20:22 ` Daniel Barkalow
2008-03-21 20:25 ` J. Bruce Fields
2008-03-22 12:12 ` Paul Gardiner
2008-03-22 16:41 ` Jeff King [this message]
2008-03-22 16:54 ` Paul Gardiner
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=20080322164136.GA7611@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=osronline@glidos.net \
/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).