From: Steven Walter <stevenrwalter@gmail.com>
To: Nigel Magnay <nigel.magnay@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn and migration
Date: Wed, 19 Dec 2007 12:54:47 -0500 [thread overview]
Message-ID: <20071219175447.GB15898@dervierte> (raw)
In-Reply-To: <320075ff0712190850r35263bcfv1d8f84e699208e15@mail.gmail.com>
On Wed, Dec 19, 2007 at 04:50:30PM +0000, Nigel Magnay wrote:
> Has anyone got any tips as I'm sure it's a path trodden before? I've
> seen examples of keeping a read-only svn, but that's not really what
> I'm after. I'm considering whether to have a central git repo
> regularly pull from svn so that it's up to date, and having us
> possibly push to svn (or git if it's not merged to trunk) as an
> interim step..
Using a central git repo that is kept uptodate with svn is the approach
I've used. git-svn isn't especially keen on this mode of operation,
however. After every fetch, you have to reset refs/remotes/trunk to
origin/master, which it turn puts .git/svn out of date (you can blow it
away and run "git svn fetch" to regenerate it).
I wrote a script that automates most of this stuff (including doing
incremental additions to git-svn's revdb/revmap). If there's interest,
I can see about cleaning it up for general consumption.
--
-Steven Walter <stevenrwalter@gmail.com>
Freedom is the freedom to say that 2 + 2 = 4
B2F1 0ECC E605 7321 E818 7A65 FC81 9777 DC28 9E8F
next prev parent reply other threads:[~2007-12-19 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <320075ff0712190849u2c40cc46pf01fa2a75f557482@mail.gmail.com>
2007-12-19 16:50 ` git-svn and migration Nigel Magnay
2007-12-19 17:54 ` Steven Walter [this message]
2007-12-19 20:23 ` Miklos Vajna
[not found] ` <320075ff0712191246r46cd76f7r1d8edc1adf35ae57@mail.gmail.com>
2007-12-19 20:47 ` Nigel Magnay
2007-12-19 21:14 ` Seth Falcon
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=20071219175447.GB15898@dervierte \
--to=stevenrwalter@gmail.com \
--cc=git@vger.kernel.org \
--cc=nigel.magnay@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).