Multiple SVN Repos Inside A Git Repo

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Multiple SVN Repos Inside A Git Repo

From: Tim Sally <hidden>
Date: 2016-06-15 22:45:43

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

Re: Multiple SVN Repos Inside A Git Repo

From: Michael J Gruber <hidden>
Date: 2016-06-15 22:45:43

Tim Sally venit, vidit, dixit 02.12.2008 21:22:
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help