From: "Santi Béjar" <santi@agolina.net>
To: demerphq <demerphq@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: Adding files to a git-archive when it is generated, and whats the best way to find out what branch a commit is on?
Date: Wed, 29 Jul 2009 11:33:04 +0200 [thread overview]
Message-ID: <adf1fd3d0907290233y78514f98h89a2fca7bf68b4f2@mail.gmail.com> (raw)
In-Reply-To: <9b18b3110907290221o8afc72s157969ef7d707d4d@mail.gmail.com>
2009/7/29 demerphq <demerphq@gmail.com>:
> 2009/7/29 Santi Béjar <santi@agolina.net>:
>> 2009/7/29 demerphq <demerphq@gmail.com>:
>>> Another question is whether anyone has any advice on the best way to
>>> find out the "best" branch an arbitrary commit is on. Where best can
>>> be flexibly definied to handle commits that are reachable from
>>> multiple branches. I have hacked a solution involving git-log and
>>> grep, but it performs quite poorly. I was wondering if there is a
>>> better solution.
>>
>> The "best" tag is easy: git describe commit. For branches I think you
>> could use "git name-ref --refs=refs/heads/* commit", because git
>> describe does not have a --branches flag.
>
> Dang, I guess this is from a newer release than mine. So now i have an
> excuse to upgrade.
No, it is quite old (the --refs flag since the v1.5.1). If the problem
is that you don't find the "git name-ref" command is because it is
"git name-rev", oops.
Santi
next prev parent reply other threads:[~2009-07-29 9:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 8:15 Adding files to a git-archive when it is generated, and whats the best way to find out what branch a commit is on? demerphq
2009-07-29 8:40 ` Avery Pennarun
2009-07-29 8:41 ` Santi Béjar
2009-07-29 9:21 ` demerphq
2009-07-29 9:33 ` Santi Béjar [this message]
2009-07-29 9:51 ` demerphq
2009-07-29 11:13 ` Santi Béjar
2009-07-30 20:33 ` René Scharfe
2009-07-31 10:04 ` demerphq
[not found] ` <m3hbwtrpip.fsf@localhost.localdomain>
2009-07-31 13:48 ` demerphq
2009-08-02 13:52 ` René Scharfe
2009-08-02 14:19 ` demerphq
2009-08-04 17:50 ` René Scharfe
2009-07-29 16:12 ` Jeff Epler
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=adf1fd3d0907290233y78514f98h89a2fca7bf68b4f2@mail.gmail.com \
--to=santi@agolina.net \
--cc=demerphq@gmail.com \
--cc=git@vger.kernel.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).