From: Jay Soffian <jaysoffian@gmail.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: git <git@vger.kernel.org>
Subject: Re: Unexpected error: short SHA1 is ambiguous
Date: Sun, 27 Jun 2010 00:02:35 -0400 [thread overview]
Message-ID: <AANLkTik_TqDoNxEbQW8lTv7l-qfCLR9ICXEabGCSGy_5@mail.gmail.com> (raw)
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.
next prev parent reply other threads:[~2010-06-27 4:02 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 [this message]
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=AANLkTik_TqDoNxEbQW8lTv7l-qfCLR9ICXEabGCSGy_5@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--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 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).