Thank you very much for the clarification. I don't think I'm able to solve
those issues.

Wouldn't it be a viable option to offer git for Windows not bundled with an
outdated svn but just use the systems svn? Then users would have to install
two programs if they decide to use git-svn. Of course i'm not sure if this
is technically feasible though. Just trying to see some workarounds because
this would give git a strategically strong position of sneaking into
existing svn systems.
On Jan 7, 2014 6:26 PM, "Konstantin Khomoutov" <> wrote:

> On Tue, 7 Jan 2014 09:04:49 -0800 (PST)
> Sebastian Bürgel <> wrote:
> > I have been using SVN on windows for a while (Tortoise) and now I am
> > trying to switch to git. Since most people in my group are SVN
> > lovers, I was quite happy seeing that I could use git with the
> > existing SVN repository that the rest of the group is using. However
> > I encounter the following problem:
> [...]
> > Your client is too old to commit to this repository.
> > A version 1.5 or later client is required.
> [...]
> > After searching around it seems that git svn is using the existing
> > SVN on the system(?)
> No, this is a wrong assumption: Git for Windows packages Subversion
> libraries with itself.  You might find them under the "bin" directory
> in your Git installation directory.
> > $ git svn --version
> > git-svn version (svn 1.4.6)
> And yes, Subversion client libraries packaged with Git for Windows are
> severely outdated.  This is an unfortunately known issue.
> > Can anyone guide me in a direction how to update git-svn to at least
> > 1.5?
> Not an easy task [1].  Many have tried and failed.  To this date, no
> one seemed to want a newer Subversion client libraries packaged badly
> enough to pass all the obstacles while dealing with this.
> 1.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to