From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
David Michael Barr <david.barr@cordelta.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: [GSoC update extra!] git-remote-svn: Week 13
Date: Sat, 31 Jul 2010 00:31:27 +0530 [thread overview]
Message-ID: <20100730190124.GA2995@kytes> (raw)
Hi,
I just got a proof-of-concept loader for Subversion working. It just
about works for a very small reduced case. I'll still have to hammer
it into shape for to handle various cases [1]. In the meantime, we
also have to start working on doing the inverse of what
svn-dump-fast-export does: convert a Git fast-export stream to a
Subversion dumpfile.
David: Can you estimate how challenging the task is going to be?
[1]: I'm working on it directly in trunk. You can find the latest code
in subversion/svnrdump in the Subversion trunk.
-- Ram
next reply other threads:[~2010-07-30 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 19:01 Ramkumar Ramachandra [this message]
2010-08-05 14:43 ` [GSoC update extra!] git-remote-svn: Week 13 David Michael Barr
2010-08-05 16:42 ` Sverre Rabbelier
2010-08-05 22:15 ` David Michael Barr
2010-08-05 22:23 ` Sverre Rabbelier
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=20100730190124.GA2995@kytes \
--to=artagnon@gmail.com \
--cc=david.barr@cordelta.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=srabbelier@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).