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

Re: git-svnimport

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Feb 4, 2006, 03:16 UTC
Message-ID
<46a038f90602031916x6cfb9e6bg7dfa0fb1cc237dac@mail.gmail.com>
In-Reply-To
<16255.1139021263@lotus.CS.Berkeley.EDU>
On 2/4/06, Jason Riedy <ejr@eecs.berkeley.edu> wrote:
Show 5 quoted lines
> Looking through the git-svnimport source makes it appear
> difficult to just snarf just one directory (maybe /) out
> of a svn repository.  Actually, it makes everything svn-
> related appear difficult.  Why should I worry about
> memory management by default in Perl?!?

I think that the SVN internals are so yucky that we're lucky to get away with "just" that bit of memory-handling crud.

>  It'd be nice if
> there were an git-svnimport-trivial that just snarfed a
> single URL without tags or branches.

We're definitely needing some updates to the doco for svnimport to make it easier. Maybe some examples of real life scenarios with different repo layouts

> I have to deal with a few repos with bizarre directory
> structures...
looks like you're the man for the job ;-)
cheers,
martin
Previous: Jason RiedyNext: Martin Langhoff
Message 3 of 4 in “git-svnimport”
  1. Jason HarrisonFeb 3, 2006
  2. Jason RiedyFeb 4, 2006
  3. Martin LanghoffFeb 4, 2006
  4. Martin LanghoffFeb 4, 2006

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.