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

Re: Subversion integration with git

From
David Michael Barr <david.barr@cordelta.com>
Date
Mar 28, 2010, 12:03 UTC
Message-ID
<4F70255B-6FCC-4020-B993-A15E6DC0E774@cordelta.com>
In-Reply-To
<4BABAA30.3080806@obry.net>
Pascal,
Show 10 quoted lines
>> My project is still in the preview phase but has enough to import 
>> commit-tree structure bar symlinks and executable flags. It imports 
>> my 22000+ commit 2.8GB dump in 4 minutes. It is currently 840 
>> non-comment lines of C. I aim to produce output that git-svn can
>> take over from.
> 
> Impressive numbers! I've converted many projects using git-svn and yes
> it is slow. Just curious, does it handles branches? Can it handles not
> standard layout (trunk/branch/tags)? When you have a git-svn compatible
> output I would be willing to test it on a project.
My initial design target is a one-to-one translation of the subversion history to a single linear git branch. I'm working under the assumption that something like git filter-branch can be used to transform the history to a more logical representation. This should allow any subversion layout to be handled.
When I have git-svn compatible output, I'll proudly announce the first release.
Previous: Pascal ObryNext: Ramkumar Ramachandra
Message 4 of 8 in “Subversion integration with git”
  1. David Michael BarrMar 25, 2010
  2. Erik Faye-LundMar 25, 2010
  3. Pascal ObryMar 25, 2010
  4. David Michael BarrMar 28, 2010
  5. Ramkumar RamachandraMar 25, 2010
  6. David Michael BarrMar 25, 2010
  7. David Michael BarrMar 30, 2010
  8. Ramkumar RamachandraMar 30, 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.