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

Experiences with git-svnimport

From
CBChristian Biesinger <cbiesinger@web.de>
Date
Feb 11, 2006, 18:22 UTC
Message-ID
<43EE2B82.5040204@web.de>
Hi,

since I now got git-svnimport to work, I thought I'd post my experiences with it, as that may be helpful for others.

I had various setups here. One of them was the usual (?) one, where I had a subversion repository at https://servername/svn, containing three projects.

One of them followed the usual structure:
   projectname/trunk
   projectname/branches/...
Now, the straightforward way would be:
   git-svnimport -C somedir https://servername/svn projectname
It turns out that this is equivalent to
   git-svnimport -C somedir https://servername/svn/projectname
if the -d or -D option is not specified, and those can't be used with https.

And that doesn't work. The problem is that the SVN repository contains urls relative to the top of the repository, i.e. /projectname/trunk/... That doesn't match the /trunk/ that's expected by svnimport.

The solution for this: Apply the patch I sent earlier and use:
   git-svnimport -v -C somedir -T projectname/trunk -b 
projectname/branches https://servername/svn/

It turned out that the other two projects on this server didn't use the trunk/branches structure (I forgot about that when setting them up), but that was not a problem: I could just do:

   git-svnimport -v -C somedir -T projectname https://servername/svn/
This also works fine for a svn+ssh:// repository.

Now, maybe my setup was unusual, and I should instead have used separate repositories for different projects. However, this worked for me, and my experiences in getting this to work might be of interest to others.

Message 1 of 1 in “Experiences with git-svnimport”
  1. Christian BiesingerFeb 11, 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.