Re: Unexpected error: short SHA1 is ambiguous

From: Jay Soffian <jaysoffian@gmail.com>
Date: Jun 27, 2010, 04:02 UTC
Message-ID: <AANLkTik_TqDoNxEbQW8lTv7l-qfCLR9ICXEabGCSGy_5@mail.gmail.com>
In-Reply-To: <alpine.LFD.2.00.1006262323310.24097@xanadu.home>

On Sat, Jun 26, 2010 at 11:35 PM, Nicolas Pitre <nico@fluxnic.net> wrote:

> No, the ^0 is not restricting anything.  It merely says you want to walk
> through zero parents from the specified commit, but the commit
> specification is ambiguous (3 possibilities exist).

Okay.

> rev-list will give you a range of commits.  But again, which range do
> you want? There are 3 possible starting points when only specifying
> aabb.

I see. Well, I guess I'd wanted something like "rev-list --no-walk --all-matches <ambiguous SHA-1>" as a way to say "return everything even if it isn't canonical".

In any case, I found a better way to go about what I was trying to do.

Thanks,

j.