Re: git-svn problem with v1.6.5

From: Eric Wong <normalperson@yhbt.net>
Date: Nov 11, 2009, 20:34 UTC
Message-ID: <20091111203413.GA9648@dcvr.yhbt.net>
In-Reply-To: <20091111202201.GA10351@dcvr.yhbt.net>

Eric Wong <normalperson@yhbt.net> wrote:

Show 17 quoted lines

> Pascal Obry <pascal@obry.net> wrote:
> > I do not see something under .git/refs/* (only empty directories).
> >
> > The project has been imported using something like this:
> >
> >  $ git svn clone --prefix=svn/ svn+ssh://server/path \
> > 	--revision=580:HEAD \
> > 	--trunk=trunk/project \
> > 	--tags=tags/project \
> > 	--branches=branches/project \
> > 	--branches="branches/global/*/project" project
> 
> It looks like you didn't use any of the weird[1] options that make it
> unsafe to clobber the rev_maps.  Can you try removing all the .rev_map.*
> files in $GIT_DIR/svn and running "git svn fetch" to rebuild them?
> 
> [1] --no-metadata, --use-svm-props

Also, any chance you have multiple refs with "trunk" in the basename?

 git rev-parse --symbolic --all | grep '/trunk'

It could be a backwards compatibility issue with git svn looking in multiple places for trunk.

With Adam's commit, it'll try $GIT_DIR/svn/refs/remotes/trunk/* first Then it'll try $GIT_DIR/svn/trunk/* as a fallback.

-- 
Eric Wong