git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Trouble with git-svn when upstream svn URL changed

From
Seth Falcon <sethfalcon@gmail.com>
Date
Dec 8, 2006, 18:34 UTC
Message-ID
<m2wt52fd8p.fsf@ziti.local>
In-Reply-To
<20061208181109.GA10475@localdomain>
Eric Wong <normalperson@yhbt.net> writes:
> This is incorrect, rebuild is not designed to handle new urls.  
ok, I was lead astray by this part of the doc for rebuild:
         A Subversion URL may be optionally specified at the
         command-line if the directory/repository you're tracking has
         moved or changed protocols.
Show 9 quoted lines
> However, git/git-svn are very flexible beasts :)
>
>> I guess I can create a fresh git repos using git-svn init and then
>> fetch all of my dev branches from the original repository.
>
> You can look at "Advanced Example: Tracking a Reorganized Repository"
> in the manpage.  Ignore the text about --follow-parent since you
> already have the old stuff fetched, and start following the instructions
> beginning with "# And now, we continue tracking the new revisions:"
Oh, sorry I didn't find that example.  This worked perfectly, thanks!
One question: My fingers are in the habit of typing remotes/git-svn.
Can I do:
   cd .git/svn
   rm -r git-svn
   mv git-newsvn git-svn

Or is there a safer way to rename? Or are there other config-file ways to make this work -- to provide an alias?

Thank you so much for the prompt reply. Nice to get going again and with the full history.

Previous: Eric WongNext: Eric Wong
Message 3 of 4 in “Trouble with git-svn when upstream svn URL changed”
  1. Seth FalconDec 8, 2006
  2. Eric WongDec 8, 2006
  3. Seth FalconDec 8, 2006
  4. Eric WongDec 8, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.