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

Re: [GSoC update] git-remote-svn: The final one

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Aug 17, 2010, 16:20 UTC
Message-ID
<AANLkTim5RYDuius6Oa6KX0weQhwVz+_YP=1-ujb3-CuJ@mail.gmail.com>
In-Reply-To
<AANLkTikyrC07OnMJWDmC7n0ks3TdOxb=jPmKWbK9Nc7u@mail.gmail.com>
Heya,
On Tue, Aug 17, 2010 at 11:10, Erik Faye-Lund <kusmabite@gmail.com> wrote:
Show 7 quoted lines
> On Tue, Aug 17, 2010 at 5:59 PM, Ramkumar Ramachandra
> <artagnon@gmail.com> wrote:
>> We're doing better than that- when the whole thing is complete, we
>> should have perfectly seamless two-way compatibility.
>
> Does this include handling SVN repos where the layout have changed
> during it's lifetime? If so, how will this look on the git side?

Perhaps it makes sense to start a new thread to hash that out for when the time comes to implement that?

-- 
Cheers,

Sverre Rabbelier
Previous: Erik Faye-LundNext: Ramkumar Ramachandra
Message 5 of 9 in “[GSoC update] git-remote-svn: The final one”
  1. Ramkumar RamachandraAug 17, 2010
  2. Stephen BashAug 17, 2010
  3. Ramkumar RamachandraAug 17, 2010
  4. Erik Faye-LundAug 17, 2010
  5. Sverre RabbelierAug 17, 2010
  6. Ramkumar RamachandraAug 17, 2010
  7. Ramkumar RamachandraAug 17, 2010
  8. Stephen BashAug 17, 2010
  9. 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.