git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Unexpected error: short SHA1 is ambiguous

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Jun 27, 2010, 19:02 UTC
Message-ID
<m2lja0wb6n.fsf@igel.home>
In-Reply-To
<alpine.LFD.2.00.1006262323310.24097@xanadu.home>
Nicolas Pitre <nico@fluxnic.net> writes:
Show 8 quoted lines
> On Sat, 26 Jun 2010, Jay Soffian wrote:
>> 1. Since I restricted to commits with ^0, and there's only one such
>> commit, shouldn't rev-list give me what I want? (rev-parse similarly
>> fails).
>
> 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).

But ^0 can only be applied to a commit, and only one commit matches aabb.

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Jay Soffian
Message 4 of 4 in “Unexpected error: short SHA1 is ambiguous”
  1. Jay SoffianJun 27, 2010
  2. Nicolas PitreJun 27, 2010
  3. Jay SoffianJun 27, 2010
  4. Andreas SchwabJun 27, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.