From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-remote-svn: Call for manpower
Date: Sun, 25 Jul 2010 15:59:10 +0530 [thread overview]
Message-ID: <20100725102908.GA2726@kytes> (raw)
Hi,
I know I've asked for this time and again, but I'll make another
request.
Short version: If there's anyone interested in git-remote-svn and has
some free time, please join the team. We currently have more work than
the team can handle, and the deadline is drawing closer.
Longer "what's cooking" version:
1. svnrdump: The version merged into trunk at subversion/svnrdump is
in excellent shape, thanks to the Subversion developers. This week,
we fixed the dump output to include missing headers, revision 0,
match the newlines from the output of `svnadmin dump`, included
authentication support, and thoroughly scrubbed the codebase.
2. Regression tests for svnrdump: Since I'm only a partial committer,
I need approval to commit outside svnrdump/ - I've already sent
patches for tests to the mailing list and am waiting for
approval. Instead of validating against 10k revisions of a
repository, there are reduced tests cases to test just the edge
cases in the trunk and we're using these- it will make the tests
easier to run, and debugging much easier.
3. svnrload: I just started working on this in branches/svnrload,
designing it as the inverse version of svnrdump. This is very
non-trivial work, and will take us atleast a few weeks to complete.
4. Dumpfilev3 support for svn-fe: Since we're running out of time,
I've decided to depend on libsvn for parsing the svndiff0, and
remove the dependency later. I should be able to finish this off in
a a few days; my current work is in the dumpfilev3 branch.
5. Zero-tree refactor: I don't really know if we'll be able to
complete this in time. I've asked Jonathan to do as little as
possible to make svn-fe Git-aware.
6. Ternary-treap refactor: This isn't strictly necessary either, and
I've decided to let David work on it in his own time.
7. Modifications to svn-fast-import: Sverre, and Jonathan: what's the
status of this?
8. Exporter for converting the fast-export stream into a dumpfilev3 to
feed svnrload: Can someone work on this?
9. Trunk/ branch/ tag mapper: I'm dropping all post-processing for the
moment. We don't have anyone to work on this, and it's independent
of everything else- it can easily be worked on later.
Thanks for reading.
-- Ram
next reply other threads:[~2010-07-25 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 10:29 Ramkumar Ramachandra [this message]
2010-07-25 19:56 ` git-remote-svn: Call for manpower Sverre Rabbelier
2010-07-25 20:18 ` Jonathan Nieder
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=20100725102908.GA2726@kytes \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
/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).