Re: git svn clone failing

From: Eric Wong <normalperson@yhbt.net>
Date: Jun 28, 2011, 04:28 UTC
Message-ID: <20110628042831.GA29202@dcvr.yhbt.net>
In-Reply-To: <BANLkTimoDBr+ikZ4XoW1y=1=_JNOtp_jfg@mail.gmail.com>

Vampire <Vampire@Masters-of-Disaster.de> wrote:

> Hm, actually I found a workaround.
> If I use https instead of http, it works fine.
> But I think it should also work with http.

This could be a server configuration issue.... More below.

Show 9 quoted lines

> 2011/6/2 Vampire <Vampire@masters-of-disaster.de>:
> > It seems to me that this happens while git-svn is searching for history.
> > As far as I have understood git-svn searches hierarchical higher paths
> > for history in other places than specified.
> > I guess while trying to access all those paths some path is tried that
> > returns 403 Forbidden.
> > My assumption is that git-svn takes this as cause to abort instead of
> > ignoring this return state what would be appropriate in this case I
> > think.

git svn should be able to avoid following old history with the --no-follow-parent option. There's also the --ignore-paths option which can ignore newer history, too. I've rarely used either (and rarely use git-svn nowadays), but one of them should work in case neither http nor https work

-- 
Eric Wong