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

Re: git-svn error: ambiguous argument

From
Bert Wesarg <bert.wesarg@googlemail.com>
Date
Jul 6, 2010, 23:11 UTC
Message-ID
<AANLkTilv1RywImw4RM3jMZl6YTawGhvodlhnX4RN1RWo@mail.gmail.com>
In-Reply-To
<20100628062409.GA13203@dcvr.yhbt.net>
On Mon, Jun 28, 2010 at 08:24, Eric Wong <normalperson@yhbt.net> wrote:
Show 11 quoted lines
> Bert Wesarg <bert.wesarg@googlemail.com> wrote:
>> On Tue, May 11, 2010 at 21:44, Paul Lindner <lindner@inuus.com> wrote:
>> > This fixed it for my situation.  Thanks!
>> > On May 11, 2010, at 9:20 AM, Bert Wesarg wrote:
>> >> Can you try this patch, it worked on my site:
>
> <snip>
>
>> Eric, have you picked this up, or should I re-send it as a propper patch?
>
> A proper patch + commit message would be easier, thanks Bert!

I have invested some time to verify my patch before sending. And I think I will break something. The current patch changes the range argument for git rev-list from "r1^..r2" to "r1^!" & "r2", which should not be the same, because "r1^..r2" is equivalent to "^r1^" & "r2". This reads 'all commits reachable from r2 but not reachable from the parent of r1' where my conversion should read 'all reachable from r1 (excluding all of its parents) or reachable from r2'. But maybe the 'excluding all of its parents'-part quarantines that the semantic still holds?

At least test 5 of t9151-svn-mergeinfo.sh does not pass, so my patch proved to be wrong.

Bert
>
> --
> Eric Wong
>
Previous: Eric Wong
Message 8 of 8 in “git-svn error: ambiguous argument”
  1. Paul LindnerMay 3, 2010
  2. Bert WesargMay 11, 2010
  3. Bert WesargMay 11, 2010
  4. Bert WesargMay 11, 2010
  5. Paul LindnerMay 11, 2010
  6. Bert WesargJun 28, 2010
  7. Eric WongJun 28, 2010
  8. Bert WesargJul 6, 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.