Eric, Any thoughts on the other patch? Am I close or is there a better way to go about this? I didn't really know what to do with .git/svn/*. The easy answer is mkdir -p $GIT_DIR/svn/refs/remotes && mv $GIT_DIR/svn/* $GIT_DIR/svn/refs/remotes >From the comments in the Migration module, it seems like that's frowned upon, so I came up with looking for .rev_map (or .rev_db) in both locations (.git/svn/git-svn and .git/svn/refs/remotes/svn) and letting it stay in whichever location it already exists. (The next email has a slightly improved version of the patch.) This solution is particularly inelegant in it's handling of unhandled.log, but as far as I know that file is unused. There's also the problem of what to do if someone has a ref called ref/remotes/refs/remotes/..., but that seems unlikely enough to not cause concern. Adam -- 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