Git 2.0 incompatability

[Larry Shatzer, Jr.]

This won't convert your tags/branches if you are running git 2.0...

I had to update Branches and Tags code to have refs/remotes/origin in place of just refs/remotes

(Example:

refs/remotes/origin/tags instead of refs/remotes/tags

Attached is a patch, however it probably would break for people not on Git 2.0 yet, so it probably needs to be massaged to account for both versions...

[Yaron Tal]

Seems like a work-around is possible by using --prefix="" when doing the clone. That should probably be added to the documentation, and maybe have something check the prefix in the script to make it a bit more dynamic?

Before Git v2.0, the default prefix was "" (no prefix). This meant that SVN-tracking refs were put at "refs/remotes/", which is incompatible with how Git’s own remote-tracking refs are organized. If you still want the old default, you can get it by passing --prefix "" on the command line (--prefix="" may not work if your Perl’s Getopt::Long is < v2.37).* http://git-scm.com/docs/git-svn

[Aaron Smalls]

Hmmm, so I added an svn prefix without realizing that it would break clean-git as well. Is there any way to fix this without doing the clone all over again. The clone on my repo takes over 12 hours.

[Jon Spencer]

This seems to have been a issue for a while now. Is there any indication of when this will be fixed for those of us (like me) who have no idea where this patch should be applied?