From: Seth Falcon <sethfalcon@gmail.com>
To: git@vger.kernel.org
Cc: Eric Wong <normalperson@yhbt.net>
Subject: Trouble with git-svn when upstream svn URL changed
Date: Fri, 08 Dec 2006 09:43:37 -0800 [thread overview]
Message-ID: <m21wnai8qe.fsf@ziti.local> (raw)
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?
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.
git version 1.4.4.1.g03c8-dirty (no changes to git-svn)
Thanks,
next reply other threads:[~2006-12-08 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 17:43 Seth Falcon [this message]
2006-12-08 18:11 ` Trouble with git-svn when upstream svn URL changed Eric Wong
2006-12-08 18:34 ` Seth Falcon
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=m21wnai8qe.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