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

Unexpected error: short SHA1 is ambiguous

From
Jay Soffian <jaysoffian@gmail.com>
Date
Jun 27, 2010, 02:16 UTC
Message-ID
<AANLkTikSUBgySbxtKO1iB-GYFgxaL5lY0mfbb5f_xxMS@mail.gmail.com>
In my copy of git.git:

$ git rev-list aabb^0 -- error: short SHA1 aabb is ambiguous. fatal: bad revision 'aabb'

$ git rev-list --all --objects | grep ^aabb aabb2e515c334cbca9d9ae9873a188cef2c9b3ba aabb9750fddbc28091c46780ccf7b835b62b04c7 Documentation/hooks.txt aabb1bcbe2b8ce00ced1a749cbab5c1646e0e1f2 Documentation

So a couple things:
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).
2. Shouldn't rev-list spit out whatever matches, even if it's
ambiguous? (I can understand that rev-parse wouldn't, but rev-list,
well, I expect a list of SHA1s from it.)
j.
Next: Nicolas Pitre
Message 1 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.