On Tue, Jun 17, 2008 at 12:06 PM, Sam Hocevar <sam@xxxxxxx> wrote: > I know this has been addressed a few times, but since I haven't found > any reasonable way to relocate a git-svn repository (after a protocol > change, or a server name change) I thought I'd share how I did it. > > Step 1 is to edit ".git/config" and modify the "url = " line so > that it reflects the new repository address. For instance: > > - url = http://svn.gnome.org/svn/gimp > + url = svn+ssh://svn.gnome.org/svn/gimp > > From now on, git-svn will basically stop working, because the > "git-svn-id:" lines in the commit logs will no longer match its > configuration. And git-filter-branch is of no use here either, because > it will change the md5sum of each commit, and git-svn will no longer be > able to track the commits. It is not so hard to work around this problem. After you run filter-branch, make sure the ref used by git-svn in refs/remotes points to the new (altered) hash. Then, delete the .git/svn/<remote> directory corresponding to the svn-remote you changed (trunk, probably). When you next run "git svn fetch", git-svn will regenerate its revmap using the new hash, and everything should be peachy after that. -- -Steven Walter <stevenrwalter@xxxxxxxxx> "A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects." -Robert Heinlein -- 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
