From: Michael Haggerty <mhagger@alum.mit.edu>
To: Dave Zarzycki <zarzycki@apple.com>
Cc: git@vger.kernel.org
Subject: Re: git svn fetch error
Date: Mon, 23 May 2011 10:16:23 +0200 [thread overview]
Message-ID: <4DDA17D7.8020504@alum.mit.edu> (raw)
In-Reply-To: <3504B354-D3F2-4419-B2EC-E14F83EC0371@apple.com>
On 05/23/2011 01:39 AM, Dave Zarzycki wrote:
> Has anybody seen the following error with git svn fetch? I've seen this both with 1.7.4.4 and top-of-tree.
>
> Argument "195270*" isn't numeric in numeric le (<=) at /usr/libexec/git-core/git-svn line 3840.
> Argument "195270*" isn't numeric in numeric le (<=) at /usr/libexec/git-core/git-svn line 3840.
> Argument "195270*" isn't numeric in numeric gt (>) at /usr/libexec/git-core/git-svn line 3822.
> Argument "195270*" isn't numeric in numeric ge (>=) at /usr/libexec/git-core/git-svn line 3823.
> Argument "195270*" isn't numeric in numeric gt (>) at /usr/libexec/git-core/git-svn line 3118.
>
> How alarmed should I be?
I haven't looked into the code, but from the argument shown in the error
message my guess is that git-svn is being confused by Subversion's
non-inheritable merge information. Non-inheritable merge information
can arise from partial-tree merges. The hairy details about
non-inheritable merge information are in the section entitled "Mergeinfo
Inheritance and Non-Inheritable Ranges" in [1].
Michael
[1] http://www.collab.net/community/subversion/articles/merge-info.html
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2011-05-23 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 23:39 git svn fetch error Dave Zarzycki
2011-05-23 8:16 ` Michael Haggerty [this message]
2011-06-19 15:57 ` Dave Abrahams
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=4DDA17D7.8020504@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=zarzycki@apple.com \
/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.