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

Re: [GSoC update] git-remote-svn: Week 11

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jul 12, 2010, 18:12 UTC
Message-ID
<20100712181233.GC17630@debian>
In-Reply-To
<1278949191.1611.5.camel@wpalmer.simply-domain>
Hi,
Will Palmer writes:
Show 5 quoted lines
> This is all moot, because the whole point is that svndumpr compiles
> against libsvn, so you don't need the whole svn source-tree. All you
> need to get svndumpr working are some header files and a working libsvn.
> Everyone who currently uses git-svn already has a working libsvn, since
> perl's svn bindings wrap around libsvn anyway.

Yes, I meant that people will need the complete Subversion tree if I DON'T get svnrdump merged somewhere in git.git (I'll attempt to get the version that compiles against libsvn 1.6 merged). The instructions to checkout the right branches and place it in the git tree can be complicated: git-remote-svn relies on a chain of tools including David's exporter and svnrdump to work.

-- Ram
Previous: Will PalmerNext: Stefan Sperling
Message 5 of 7 in “[GSoC update] git-remote-svn: Week 11”
  1. Ramkumar RamachandraJul 12, 2010
  2. Michael J GruberJul 12, 2010
  3. Stefan SperlingJul 12, 2010
  4. Will PalmerJul 12, 2010
  5. Ramkumar RamachandraJul 12, 2010
  6. Stefan SperlingJul 14, 2010
  7. Michael J GruberJul 12, 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.