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

Re: question: connecting to multiple remote svn projects

From
Avery Pennarun <apenwarr@gmail.com>
Date
Nov 6, 2009, 19:51 UTC
Message-ID
<32541b130911061151q68ddcc58w209acf28c5eec2f@mail.gmail.com>
In-Reply-To
<hd1nv2$79e$1@ger.gmane.org>
On Fri, Nov 6, 2009 at 12:55 PM, Dave Rodgman <dav1dr@eml.cc> wrote:
Show 14 quoted lines
> Given a layout in a single subversion repository like this:
>
> module1/branches/1.0/work
> module2/branches/1.0/work
>
> I would like achieve the following layout locally, in git:
>
> module1/work
> module2/work
>
> Obviously I can create multiple git repositories in separate directories,
> but I would like them to be in a single repository. I can also get the
> same layout as subversion, but this breaks various bits of build
> infrastructure.

Can you just create the file structure you want using symlinks? That would be the easiest way.

> I don't care about tracking the subversion branches in git, or being able
> to switch between subversion branches.

Don't care about tracking *any* subversion history, or just the history of branches other than the 1.0 branch you've listed above? I assume the latter, because otherwise the problem is easy (just copy the latest revision of the files into a git repo and commit).

Other options that might work for you: create a "superproject" branch and import the two modules using git-submodule, or else import them using git-subtree (http://github.com/apenwarr/git-subtree). Or import the svn history and then use git-filter-branch to move stuff around.

Good luck.
Avery
Previous: Dave RodgmanNext: Dave Rodgman
Message 2 of 4 in “question: connecting to multiple remote svn projects”
  1. Dave RodgmanNov 6, 2009
  2. Avery PennarunNov 6, 2009
  3. Dave RodgmanNov 9, 2009
  4. Avery PennarunNov 9, 2009

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.