From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: "Sverre Rabbelier" <srabbelier@gmail.com>,
"Greg Stein" <gstein@gmail.com>,
"Stefan Sperling" <stsp@elego.de>,
"Daniel Shahaf" <d.s@daniel.shahaf.name>,
"Will Palmer" <wmpalmer@gmail.com>,
"David Michael Barr" <david.barr@cordelta.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Bert Huijben" <rhuijben@collab.net>,
"Sam Vilain" <sam@vilain.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [GSoC update] git-remote-svn: Week 11
Date: Mon, 12 Jul 2010 16:35:46 +0200 [thread overview]
Message-ID: <20100712143546.GA17630@debian> (raw)
Hi,
I'm happy to report that I'll soon be getting partial committer access
to the ASF repository (thanks to Greg for this) and will be able to
commit the svnrdump there. At the moment, all the validations pass
without any issues and I've shifted my focus towards writing a
dumpfile v3 parser [1] to get the data into David's exporter. I will
re-roll a series for git.git in some time again after I've fixed a few
pending things pointed out by Jonathan in his excellent reviews and
merged a few patches from Will; although this isn't top priority, it
will be pretty painful for Git developers to compile the SVN trunk
even if they want to try out git-remote-svn.
Currently, I'm implementing svndiff0 parser component of the dumpfile
v3 parser using Sam's Perl implementation [2] as a guideline. In
addition, with an excellent specification present in the Subversion
trunk [3], this shouldn't be a problem.
-- Ram
[1]: dumpfilev3 branch of
http://github.com/artagnon/svn-dump-fast-export/
[2]: http://search.cpan.org/~samv/Parse-SVNDiff/
[3]: http://svn.apache.org/repos/asf/subversion/trunk/notes/svndiff
next reply other threads:[~2010-07-12 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 14:35 Ramkumar Ramachandra [this message]
2010-07-12 14:48 ` [GSoC update] git-remote-svn: Week 11 Michael J Gruber
2010-07-12 15:24 ` Stefan Sperling
2010-07-12 15:39 ` Will Palmer
2010-07-12 18:12 ` Ramkumar Ramachandra
2010-07-14 8:58 ` Stefan Sperling
2010-07-12 16:00 ` Michael J Gruber
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=20100712143546.GA17630@debian \
--to=artagnon@gmail.com \
--cc=avarab@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=david.barr@cordelta.com \
--cc=git@vger.kernel.org \
--cc=gstein@gmail.com \
--cc=jrnieder@gmail.com \
--cc=rhuijben@collab.net \
--cc=sam@vilain.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).