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

From: Eric Wong <normalperson@yhbt.net>
Date: Dec 8, 2006, 18:11 UTC
Message-ID: <20061208181109.GA10475@localdomain>
In-Reply-To: <m21wnai8qe.fsf@ziti.local>

Seth Falcon <sethfalcon@gmail.com> wrote:

Show 19 quoted lines

> Hi,
> 
> One of the repositories I have been tracking with git-svn was
> reorganized and the path that I have been tracking is now in a new
> location.
> 
> I was hoping that the following would work:
> 
>    git clone orig new
>    cd new
>    git svn rebuild $NEW_URL
> 
> I also tried 
> 
>    git svn rebuild --remote $NEW_URL
> 
> This have some output that looked reasonable (svn rev nums and git
> sha1's).  But git svn fetch does nothing and I don't seem to have any
> of the new content.  Am I using this incorrectly?

This is incorrect, rebuild is not designed to handle new urls. 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:"

If that fails (I don't think it would); you can always link branches together using grafts (git-svn graft-branches tries to automate this; but it's imperfect).