cho wrote: > I've surprised myself but yes, there is a simple testcase. > > svnadmin create repo > svn checkout file://$PWD/repo checkout > cd checkout/ > svn mkdir trunk tags branches > svn ci -m 'Standard svn layout.' > cd trunk/ > svn mkdir doc > touch doc/README > svn add doc/README > svn ci -m 'Add README.' > cd .. > svn mv trunk/ branches/oldtrunk > svn ci -m 'Moved trunk.' > svn mkdir trunk > svn ci -m 'New trunk.' > cd trunk/ > touch THIS_IS_THE_NEW_TRUNK > svn add THIS_IS_THE_NEW_TRUNK > svn ci -m 'Add marker.' > cd ../.. > git svn clone file://$PWD/repo --stdlayout git-clone > cd git-clone/ > tree > > So the testcase basically involves moving the trunk. > git-svn gets very confused and keeps a mixture of the old and new trunk. Were you using --follow-parent or not? Sam. - 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
