From: Andreas Schwab <schwab@linux-m68k.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Jay Soffian <jaysoffian@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Unexpected error: short SHA1 is ambiguous
Date: Sun, 27 Jun 2010 21:02:56 +0200 [thread overview]
Message-ID: <m2lja0wb6n.fsf@igel.home> (raw)
In-Reply-To: <alpine.LFD.2.00.1006262323310.24097@xanadu.home> (Nicolas Pitre's message of "Sat, 26 Jun 2010 23:35:24 -0400 (EDT)")
Nicolas Pitre <nico@fluxnic.net> writes:
> 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."
prev parent reply other threads:[~2010-06-27 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 2:16 Unexpected error: short SHA1 is ambiguous Jay Soffian
2010-06-27 3:35 ` Nicolas Pitre
2010-06-27 4:02 ` Jay Soffian
2010-06-27 19:02 ` Andreas Schwab [this message]
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=m2lja0wb6n.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=nico@fluxnic.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.