git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Stephen Bash <bash@genarts.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
	"David Michael Barr" <david.barr@cordelta.com>,
	"Daniel Shahaf" <d.s@daniel.shahaf.name>,
	"Stefan Sperling" <stsp@elego.de>,
	"Bert Huijben" <rhuijben@collab.net>,
	"Sverre Rabbelier" <srabbelier@gmail.com>,
	"Will Palmer" <wmpalmer@gmail.com>,
	"Philip Martin" <philip.martin@wandisco.com>,
	"Jonas Gehring" <jonas.gehring@boolsoft.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [GSoC update] git-remote-svn: The final one
Date: Tue, 17 Aug 2010 22:11:27 +0530	[thread overview]
Message-ID: <20100817164125.GE6947@kytes> (raw)
In-Reply-To: <27168737.115723.1282062015125.JavaMail.root@mail.hq.genarts.com>

Hi Stephen,

Stephen Bash writes:
> > > So being selfish, what I care about is an improved method for
> > > converting SVN repos to git repos once and never going back. It
> > > sounds to me like the major hurdles remaining there are getting
> > > svn-fe to handle dumpfile v3 and handling branches/tags. Is that
> > > correct?
> > 
> > We're doing better than that- when the whole thing is complete, we
> > should have perfectly seamless two-way compatibility.
> 
> That makes complete sense.  It just happens I'm interested in a subset of the problem (the order has come down from on high that we will be using git for future development), so I'm curious if/how a one-time conversion simplifies things.

Thanks for bringing this up- it's quite interesting :)

A one-time conversion thing would have changed our priorities. Mainly,
I wouldn't have been able to justify the time I invested in building
svnrdump. I'd have probably settled for complete mirror + dump using a
combination of existing tools. The second difference:
svn-dump-fast-export is quite complex; although it was probably an
unconcious decision on David's part, it makes a really good generic
parser, and I suspect that it'll help us generate the dumpfile we need
for loading revision history data back into Subversion. Third, it
simplifies the branch/ tag mapper greatly- we'd only need to achieve a
perfect one-way mapping. A symmetric mapping is harder for several
reasons- consider preserving props for instance.

-- Ram

      reply	other threads:[~2010-08-17 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 14:42 [GSoC update] git-remote-svn: The final one Ramkumar Ramachandra
2010-08-17 15:48 ` Stephen Bash
2010-08-17 15:59   ` Ramkumar Ramachandra
2010-08-17 16:10     ` Erik Faye-Lund
2010-08-17 16:20       ` Sverre Rabbelier
2010-08-17 17:18         ` Ramkumar Ramachandra
2010-08-17 16:22       ` Ramkumar Ramachandra
2010-08-17 16:20     ` Stephen Bash
2010-08-17 16:41       ` Ramkumar Ramachandra [this message]

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=20100817164125.GE6947@kytes \
    --to=artagnon@gmail.com \
    --cc=avarab@gmail.com \
    --cc=bash@genarts.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=david.barr@cordelta.com \
    --cc=git@vger.kernel.org \
    --cc=jonas.gehring@boolsoft.org \
    --cc=jrnieder@gmail.com \
    --cc=philip.martin@wandisco.com \
    --cc=rhuijben@collab.net \
    --cc=srabbelier@gmail.com \
    --cc=stsp@elego.de \
    --cc=wmpalmer@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).