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

SVN bridge for multiple SVN modules

From
RDRichard Dallaway <dallaway@gmail.com>
Date
Apr 13, 2010, 07:34 UTC
Message-ID
<m2ue3041f5c1004130034h51eb196dke0ebb8b3634e7302@mail.gmail.com>
Hello

We've run into something we'd like to do with "git svn clone" that looks like it should work, but doesn't appear to.

The task: we have an SVN repository with 38 modules in it (each with their own branches, tags, and trunk) and we'd like to pull just two of the modules into a single git repository -- but maintain the ability to perform git svn rebase/fetch/dcommit as the SVN repository is remaining active for some developers.

It looks like we should be able to point at the parent of the SVN modules and use --ignore-paths=/a long regexp/ to do the job, but we've not managed to get it to work yet and we're now wondering if we're missing a few concepts in the git/svn bridging concepts. Or maybe we've just not got the syntax right yet.

There's a related question we spotted on stackoverflow that indicates this isn't possible:

http://stackoverflow.com/questions/898568/multiple-svn-projects-into-one-git-repository

If that is the case (can anyone confirm?), is there a way we can do this by pulling each SVN module into a separate intermediate git repository, then doing "something" to push on to our target single repository.... a "something" that would still enable us to git svn fetch and git svn dcommit back to the SVN repo?

Suggestions, clues, explanations all very welcome.

Regards Richard

Next: Steven Michalske
Message 1 of 3 in “SVN bridge for multiple SVN modules”
  1. Richard DallawayApr 13, 2010
  2. Steven MichalskeApr 14, 2010
  3. Richard DallawayApr 14, 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.