From: Seth Falcon <sethfalcon@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: Trouble with git-svn when upstream svn URL changed
Date: Fri, 08 Dec 2006 10:34:30 -0800 [thread overview]
Message-ID: <m2wt52fd8p.fsf@ziti.local> (raw)
In-Reply-To: <20061208181109.GA10475@localdomain> (Eric Wong's message of "Fri, 8 Dec 2006 10:11:09 -0800")
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.
> 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.
next prev parent reply other threads:[~2006-12-08 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 17:43 Trouble with git-svn when upstream svn URL changed Seth Falcon
2006-12-08 18:11 ` Eric Wong
2006-12-08 18:34 ` Seth Falcon [this message]
2006-12-08 19:13 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wt52fd8p.fsf@ziti.local \
--to=sethfalcon@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox