From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-remote-svn: Future development timeline
Date: Tue, 17 Aug 2010 22:46:14 +0530 [thread overview]
Message-ID: <20100817171611.GF6947@kytes> (raw)
Hi,
The ETA for completion of git-remote-svn is three months. Here's a
relatively short-term plan.
I'm currently writing the dumpfilev3 support into svn-dump-fast-export
with two of Jonathan's patches applied [1]:
'Teach fast-import to import subtrees named by tree id' and
'Teach fast-import to print the id of each imported commit'
The first is already in `pu` and I've just ressurected the discussion
pertaining to the second. Since I already have a stopgap svndiff0
parser, I can work on re-implementing a better parser while
simultaneously working on dumpfilev3 support. I expect to have made
some significant progress by this weekend. Depending on the
fast-import patch, I expect that this'll take upwards of a month to
complete.
I'm also simultaneously working on cleaning up `svnrdump` and
abstracting out many of its components as a reusable library. The work
is pretty light, and there's no hurry to finish this off.
The branch/ tag mapper needs more thought and sketching out. I'll
think about this harder, mock up a few models, and put up some serious
notes next week for discussion.
I'll defer the conversion from the fast-export stream to dumpfilev3
for now.
As usual, everyone is welcome to join in.
[1] The work's in a bit of a mess, but I'll soon rebase it on
`pu-base` on http://github.com/artagnon/git
-- Ram
reply other threads:[~2010-08-17 17:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100817171611.GF6947@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.