Hi again, Christopher Snapp wrote: > If you remember my old project's trunk has been copied to a > subdirectory of the new project's trunk. So, oldproj/trunk is now > newproj/trunk/oldproj. Yeah, I was ignoring this part. :) git svn is not really wired for it. The instructions were meant to also be usable in a case where oldproj and newproj are entirely independent repositories. > When I do a git svn clone of the newproj I > would expect it to follow the svn copy that created > newproj/trunk/oldproj but it doesn't. If the layout has been relatively stable before, maybe "git svn --no-follow-parent" would give some joy. Still I would be interested in hearing where the grafting procedure went wrong. If you end up tracking it down to a single step, do please let us know. Regards, Jonathan -- 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