Re: Possible BUG with git-rev-list --all in a StGit repository

From: Marco Costalba <mcostalba@gmail.com>
Date: Nov 28, 2006, 07:57 UTC
Message-ID: <e5bfff550611272357w33756febud0bbbe59e2e1e140@mail.gmail.com>
In-Reply-To: <7vzmadl5b0.fsf@assigned-by-dhcp.cox.net>

On 11/27/06, Junio C Hamano <junkio@cox.net> wrote:

Show 15 quoted lines

> "Marco Costalba" <mcostalba@gmail.com> writes:
>
> > Could a possible '--all-branches' new option come to rescue?
>
> I doubt it.  Next thing people would start talking about is what
> to do with the remote tracking branches, and what we are talking
> about is rev-list, one of the lower level of plumbing that would
> be better left without knowing much about the Porcelain's use of
> refs/ namespaces.
>
> If you (as a Porcelain) want to get all refs under refs/heads/,
> there are (unfortunately) two ways to get that list.  I would
> suggest obtain the refs you want that way, pass them as command
> line arguments to rev-list.
>

Unfortunatly that does not work in case a branch and a tag have the same name.

I was bitten by this trying to do what you now suggest, there were a tag and a branch called 'test', and calling

git-rev-list master origin test

raised a warning.

Only among the _same_ 'family' (branches, tags, etc..) unique names are enforced.