git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: git <git@vger.kernel.org>
Subject: Unexpected error: short SHA1 is ambiguous
Date: Sat, 26 Jun 2010 22:16:42 -0400	[thread overview]
Message-ID: <AANLkTikSUBgySbxtKO1iB-GYFgxaL5lY0mfbb5f_xxMS@mail.gmail.com> (raw)

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.

             reply	other threads:[~2010-06-27  2:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27  2:16 Jay Soffian [this message]
2010-06-27  3:35 ` Unexpected error: short SHA1 is ambiguous Nicolas Pitre
2010-06-27  4:02   ` Jay Soffian
2010-06-27 19:02   ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikSUBgySbxtKO1iB-GYFgxaL5lY0mfbb5f_xxMS@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).