{"thread":{"id":"43733","subject":"Re: Trouble with git-svn when upstream svn URL changed","startedAt":"2006-12-08T17:43:37Z","lastAt":"2006-12-08T19:13:01Z","messageCount":4,"participants":["Eric Wong","Seth Falcon"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"297660","messageId":"m21wnai8qe.fsf@ziti.local","threadId":"43733","inReplyTo":null,"subject":"Trouble with git-svn when upstream svn URL changed","fromName":"Seth Falcon","fromEmail":"sethfalcon@gmail.com","sentAt":"2006-12-08T17:43:37Z","receivedAt":"2006-12-08T17:43:37Z","isPatch":false,"sender":{"key":"sethfalcon@gmail.com","avatar":"https://gravatar.com/avatar/fd62fe73d3013b12fce71d5269ec52eaca3c4cee479efc6eea3603d6f1d8bf8d?d=mp&s=160"},"body":"Hi,\n\nOne of the repositories I have been tracking with git-svn was\nreorganized and the path that I have been tracking is now in a new\nlocation.\n\nI was hoping that the following would work:\n\n git clone orig new\n cd new\n git svn rebuild $NEW_URL\n\nI also tried \n\n git svn rebuild --remote $NEW_URL\n\nThis have some output that looked reasonable (svn rev nums and git\nsha1's). But git svn fetch does nothing and I don't seem to have any\nof the new content. Am I using this incorrectly?\n\nI guess I can create a fresh git repos using git-svn init and then\nfetch all of my dev branches from the original repository.\n\ngit version 1.4.4.1.g03c8-dirty (no changes to git-svn)\n\nThanks,\n\n"},{"id":"297528","messageId":"20061208181109.GA10475@localdomain","threadId":"43733","inReplyTo":"m21wnai8qe.fsf@ziti.local","subject":"Re: Trouble with git-svn when upstream svn URL changed","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2006-12-08T18:11:09Z","receivedAt":"2006-12-08T18:11:09Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Seth Falcon wrote:\n> Hi,\n> \n> One of the repositories I have been tracking with git-svn was\n> reorganized and the path that I have been tracking is now in a new\n> location.\n> \n> I was hoping that the following would work:\n> \n> git clone orig new\n> cd new\n> git svn rebuild $NEW_URL\n> \n> I also tried \n> \n> git svn rebuild --remote $NEW_URL\n> \n> This have some output that looked reasonable (svn rev nums and git\n> sha1's). But git svn fetch does nothing and I don't seem to have any\n> of the new content. Am I using this incorrectly?\n\nThis is incorrect, rebuild is not designed to handle new urls. However,\ngit/git-svn are very flexible beasts :)\n\n> I guess I can create a fresh git repos using git-svn init and then\n> fetch all of my dev branches from the original repository.\n\nYou can look at \"Advanced Example: Tracking a Reorganized Repository\"\nin the manpage. Ignore the text about --follow-parent since you\nalready have the old stuff fetched, and start following the instructions\nbeginning with \"# And now, we continue tracking the new revisions:\"\n\nIf that fails (I don't think it would); you can always link branches\ntogether using grafts (git-svn graft-branches tries to automate this;\nbut it's imperfect).\n\n-- \n"},{"id":"297615","messageId":"m2wt52fd8p.fsf@ziti.local","threadId":"43733","inReplyTo":"20061208181109.GA10475@localdomain","subject":"Re: Trouble with git-svn when upstream svn URL changed","fromName":"Seth Falcon","fromEmail":"sethfalcon@gmail.com","sentAt":"2006-12-08T18:34:30Z","receivedAt":"2006-12-08T18:34:30Z","isPatch":false,"sender":{"key":"sethfalcon@gmail.com","avatar":"https://gravatar.com/avatar/fd62fe73d3013b12fce71d5269ec52eaca3c4cee479efc6eea3603d6f1d8bf8d?d=mp&s=160"},"body":"Eric Wong writes:\n> This is incorrect, rebuild is not designed to handle new urls. \n\nok, I was lead astray by this part of the doc for rebuild:\n\n A Subversion URL may be optionally specified at the\n command-line if the directory/repository you're tracking has\n moved or changed protocols.\n\n> However, git/git-svn are very flexible beasts :)\n>\n>> I guess I can create a fresh git repos using git-svn init and then\n>> fetch all of my dev branches from the original repository.\n>\n> You can look at \"Advanced Example: Tracking a Reorganized Repository\"\n> in the manpage. Ignore the text about --follow-parent since you\n> already have the old stuff fetched, and start following the instructions\n> beginning with \"# And now, we continue tracking the new revisions:\"\n\nOh, sorry I didn't find that example. This worked perfectly, thanks!\n\nOne question: My fingers are in the habit of typing remotes/git-svn.\nCan I do:\n cd .git/svn\n rm -r git-svn\n mv git-newsvn git-svn\n\nOr is there a safer way to rename? Or are there other config-file\nways to make this work -- to provide an alias?\n\nThank you so much for the prompt reply. Nice to get going again and\nwith the full history.\n\n"},{"id":"298183","messageId":"20061208191301.GA13944@localdomain","threadId":"43733","inReplyTo":"m2wt52fd8p.fsf@ziti.local","subject":"Re: Trouble with git-svn when upstream svn URL changed","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2006-12-08T19:13:01Z","receivedAt":"2006-12-08T19:13:01Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Seth Falcon wrote:\n> Eric Wong writes:\n> > This is incorrect, rebuild is not designed to handle new urls. \n> \n> ok, I was lead astray by this part of the doc for rebuild:\n> \n> A Subversion URL may be optionally specified at the\n> command-line if the directory/repository you're tracking has\n> moved or changed protocols.\n\nHmm.. it seems that rebuild will work as intended iff you didn't clone\n(and therefore still have .git/svn/git-svn/.rev_db intact). Otherwise,\nit will rebuild the .rev_db file and ignore your specified URL. Perhaps\nrunning rebuild twice (specifying the URL on a second clone) after a\nclone would work. I honestly haven't used or looked at rebuild in a\nwhile.\n\n> > However, git/git-svn are very flexible beasts :)\n> >\n> >> I guess I can create a fresh git repos using git-svn init and then\n> >> fetch all of my dev branches from the original repository.\n> >\n> > You can look at \"Advanced Example: Tracking a Reorganized Repository\"\n> > in the manpage. Ignore the text about --follow-parent since you\n> > already have the old stuff fetched, and start following the instructions\n> > beginning with \"# And now, we continue tracking the new revisions:\"\n> \n> Oh, sorry I didn't find that example. This worked perfectly, thanks!\n> \n> One question: My fingers are in the habit of typing remotes/git-svn.\n> Can I do:\n> cd .git/svn\n> rm -r git-svn\n> mv git-newsvn git-svn\n> \n> Or is there a safer way to rename? Or are there other config-file\n> ways to make this work -- to provide an alias?\n\nYou need to mv refs/remotes/git-newsvn refs/remotes/git-svn, too. Then\nit should be safe.\n\n-- \n"}]}