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?

From: Santi Béjar <santi@agolina.net>
Date: Jul 29, 2009, 09:33 UTC
Message-ID: <adf1fd3d0907290233y78514f98h89a2fca7bf68b4f2@mail.gmail.com>
In-Reply-To: <9b18b3110907290221o8afc72s157969ef7d707d4d@mail.gmail.com>

2009/7/29 demerphq <demerphq@gmail.com>:

Show 15 quoted lines

> 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