Re: git-svn, tree moves, and --no-stop-on-copy

[Yann Dirson <ydirson@altern.org>]

On Tue, Mar 07, 2006 at 05:42:07PM -0800, Eric Wong wrote:
> If you want full repository history for reorganized repositories,
> easiest way is to pay the price for full repository and all of its
> history.
> 
> 	git-svn init https://svn.sourceforge.net/svnroot/ufoai
> 	git-svn fetch
> 	# this puts all your branches and tags into one single big git tree.
> 
> However, the following should always work: (after the following patch,
> 
> 	GIT_SVN_ID=git-oldsvn git-svn init \
> 		https://svn.sourceforge.net/svnroot/ufoai/trunk
> 	GIT_SVN_ID=git-oldsvn git-svn fetch -r1:165
> 
> 	GIT_SVN_ID=git-newsvn git-svn init
> 		https://svn.sourceforge.net/svnroot/ufoai/ufoai/trunk
> 	GIT_SVN_ID=git-newsvn git-svn fetch \
> 		166=`git-rev-parse refs/remotes/git-oldsvn`

Thanks much for the hint - it should definitively be a good example
for the doc.

> Unfortunately, it does not, at least with svn 1.2.3...  I have a patch
> coming that should fix things for 1.1.1 (and give better 1.1.x support
> in general).  I'm not sure, but it feels like something is screwed up
> with svn 1.2.3dfsg1-3:
> 
> This works:	svn log -r1 https://svn.sourceforge.net/svnroot/ufoai/trunk

> This doesn't:	svn  co -r1 https://svn.sourceforge.net/svnroot/ufoai/trunk
> 
> But this:	svn  co -r1 https://svn.sourceforge.net/svnroot/ufoai
> will create the following structure:
> 	ufoai/{trunk,branches,tags}
> 
> I'm quite puzzled about it, as I swear I've seen it work on a different
> project recently (of course I cannot remember which :<)

Looks like svn may be looking at the current revision to find out
which path you are requesting, and that path does not exist any more.
Could look like something normal, if "svn log" complained - but the
problem may just be with "svn log".

OTOH, this does work:

 svn co -r1 https://svn.sourceforge.net/svnroot/ufoai/trunk@1


> In the face of repository reorgs, git-svn is happiest tracking partial
> history.  Or tracking the entire repository from the root.

Well, that could be a solution, if I could 1) filter out parts of the
tree I do not care about, and 2) strip the leading /whatever/trunk.
Not sure it's worth it :)


> Hopefully I've been reasonably coherent, having insomnia lately.

At least, my state of insomnia makes it look perferctly coherent :)

Best regards,
-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>