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

Re: Multiple SVN Repos Inside A Git Repo

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Dec 3, 2008, 13:57 UTC
Message-ID
<49369066.7030101@drmicha.warpmail.net>
In-Reply-To
<4753154c0812021222t2886f986id2b775f90d4ea7f@mail.gmail.com>
Tim Sally venit, vidit, dixit 02.12.2008 21:22:
Show 20 quoted lines
> Using git-svn, it is possible to have different parts of a git repo
> correspond to a specific svn repo? From my understanding after reading
> the documentation, you need one git repository per svn.  My example is
> that I'm trying to set up a git repo to version control everything
> from my classes, but each class has a separate svn repo.  Also, the
> number of git repos I can create is limited, and I'd rather not
> clutter everything up with many separate git-svn repos.
> 
> Example structure:
> 
> class/
> .......... systems/
> .......... algorithms/
> .......... physics/
> 
> class is one central git repository, and systems, algorithms, and
> physics contain data from three svn repositories.  Ideally, you could
> commit/update to/from each svn repo individually, or all at once.
> 
> Tim

You can have as many git svn configurations in a single git repo as you want (see the "-R" argument to git svn). They will all correspond to different remote branches. By checking out the branches (or a corresponding tracking branch) you can switch between the branches, i.e. between classes.

I don't think a layout as above is possible given your requirements that
- you (basically) want a single git repo and
- you want to be able to commit back.
They exclude using submodules resp. subtree merge.
Michael
Previous: Tim Sally
Message 2 of 2 in “Multiple SVN Repos Inside A Git Repo”
  1. Tim SallyDec 2, 2008
  2. Michael J GruberDec 3, 2008

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.