From: Sam Vilain <sam@vilain•net>
To: Eric Wong <normalperson@yhbt•net>
Cc: Eric Hanchrow <eric.hanchrow@gmail•com>,
git@vger•kernel.org, Andrew Myrick <amyrick@apple•com>
Subject: Re: [spf:guess] Re: Bug? git-svn clone dies with "fatal: ambiguous argument '...': unknown revision or path not in the working tree."
Date: Fri, 15 Jan 2010 12:57:30 +1300 [thread overview]
Message-ID: <4B4FAF6A.2070407@vilain.net> (raw)
In-Reply-To: <20100113052958.GA23182@dcvr.yhbt.net>
Eric Wong wrote:
>> It chugged along happily for a while, but then died like this:
>>
>> fatal: ambiguous argument
>> '2d2df13977551168a54ffa9b706484242a58736a^..d038748d49a0de5802fe3c13f46d0e080d064290':
>>
> [...]
> As we see below, d038748d49a0de5802fe3c13f46d0e080d064290 is a merge
> commit. So I'll Cc Sam and Andrew on this since they know their way
> around the mergeinfo stuff far better than I do and will hopefully have
> some insight into things.
>
> Since it's probably related to the new mergeinfo handling, reverting to
> a version without it (1.6.5.7) might be the best way to go for now.
>
I'm at a loss. I can't get my rev-list to say "ambiguous argument" when
I pass it a similar range (eg d4e1b47a9225^..a24a32dd on git.git). Why
does it matter that the d038748 commit is a merge commit?
Eric H, is this repository available publicly for me to test? I guess
it's possible that argument is not being passed to rev-list but to some
other command ... would be nice to be able to reproduce it.
Sam
prev parent reply other threads:[~2010-01-14 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 23:58 Bug? git-svn clone dies with "fatal: ambiguous argument '...': unknown revision or path not in the working tree." Eric Hanchrow
2010-01-13 5:29 ` Eric Wong
2010-01-14 23:57 ` Sam Vilain [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=4B4FAF6A.2070407@vilain.net \
--to=sam@vilain$(echo .)net \
--cc=amyrick@apple$(echo .)com \
--cc=eric.hanchrow@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=normalperson@yhbt$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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