All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Dan Kaplan <dank@mirthcorp.com>
Cc: git@vger.kernel.org
Subject: Re: A question about the error: svn_fspath__is_canonical
Date: Fri, 10 Jan 2014 11:16:50 -0800	[thread overview]
Message-ID: <20140110191650.GF4776@google.com> (raw)
In-Reply-To: <CABRpx=1CvB55zeL1L8QOvyfbJCaG9FK+HEz-iK9cFGrnxmOJtg@mail.gmail.com>

Hi Dan,

Dan Kaplan wrote:

> My environment is probably different from most.  I'm using cygwin.
> This makes it very difficult to use different versions of
> git/svn/git-svn, but I'm interested in learning git more so I'm
> willing to try whatever it takes.
>
> $ git version
> git version 1.8.3.4
>
> $ svn --version
> svn, version 1.8.5 (r1542147)
>    compiled Nov 25 2013, 10:45:07 on x86_64-unknown-cygwin

You have three choices:

 A) upgrade git to latest "master"
 B) upgrade subversion to latest "trunk"
 C) downgrade subversion to a version before that bug was introduced

(A) is probably simplest.  E.g., something like the following should work:

  git clone https://kernel.googlesource.com/pub/scm/git/git.git
  cd git
  make -j8
  make test; # optional, to verify that the git you built works ok
  export PATH=$(pwd)/bin-wrappers:$PATH

Now the updated git is in your $PATH and you can use it.

See INSTALL in the git source tree for more details.

Hope that helps,
Jonathan

  reply	other threads:[~2014-01-10 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 19:06 A question about the error: svn_fspath__is_canonical Dan Kaplan
2014-01-10 19:16 ` Jonathan Nieder [this message]
2014-01-10 19:22   ` Dan Kaplan
2014-01-10 19:28     ` Jonathan Nieder
2014-01-10 19:34       ` Torsten Bögershausen
2014-01-10 20:36         ` Dan Kaplan

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=20140110191650.GF4776@google.com \
    --to=jrnieder@gmail.com \
    --cc=dank@mirthcorp.com \
    --cc=git@vger.kernel.org \
    /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.