git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-remote-svn: Future development timeline

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Aug 17, 2010, 17:16 UTC
Message-ID
<20100817171611.GF6947@kytes>
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
Message 1 of 1 in “git-remote-svn: Future development timeline”
  1. Ramkumar RamachandraAug 17, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.