Vampire <Vampire@xxxxxxxxxxxxxxxxxxxxxx> 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. > 2011/6/2 Vampire <Vampire@xxxxxxxxxxxxxxxxxxxxxx>: > > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html