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 21:29:37 +0530	[thread overview]
Message-ID: <20100817155933.GB6947@kytes> (raw)
In-Reply-To: <15605020.115671.1282060094242.JavaMail.root@mail.hq.genarts.com>

Hi Stephen,

Stephen Bash writes:
> Ram-
> 
> First, congratulations on making it through GSoC.  I've been avidly following your progress since our off-list discussion at the beginning of the summer, and I'm excited to watch the work continue.

Thank you :)

> > 1. Getting the revision history out of Subversion in a sane format
> > (dumpfile v3).
> >      ...
> > 2. Converting the revision history from dumpfile v3 format into a git
> > fast-import stream.
> >      ...
> > 5. Stitching everything together with a remote helper
> > application.
> >      ...
> > 6. A branch/tag mapper.
> 
> 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. But yes, you're
right- there are several non-trivial tasks to handle, the top three of
which are:
1. Making svn-fe git-aware (and hence handle dumpfile v3)
2. Writing a fast-export to dumpfilev3 converter
3. Implementing the branch/ tag mapper in an extensible way

Don't worry about it though- we're all working hard on it :)

-- Ram

  reply	other threads:[~2010-08-17 16:01 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 [this message]
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

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=20100817155933.GB6947@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).