{"thread":{"id":"16564","subject":"Multiple SVN Repos Inside A Git Repo","startedAt":"2008-12-02T20:22:46Z","lastAt":"2008-12-03T13:57:58Z","messageCount":2,"participants":["Tim Sally","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"96980","messageId":"4753154c0812021222t2886f986id2b775f90d4ea7f@mail.gmail.com","threadId":"16564","inReplyTo":null,"subject":"Multiple SVN Repos Inside A Git Repo","fromName":"Tim Sally","fromEmail":"tsally2@gmail.com","sentAt":"2008-12-02T20:22:46Z","receivedAt":"2008-12-02T20:22:46Z","isPatch":false,"sender":{"key":"tsally2@gmail.com","avatar":null},"body":"Using git-svn, it is possible to have different parts of a git repo\ncorrespond to a specific svn repo? From my understanding after reading\nthe documentation, you need one git repository per svn.  My example is\nthat I'm trying to set up a git repo to version control everything\nfrom my classes, but each class has a separate svn repo.  Also, the\nnumber of git repos I can create is limited, and I'd rather not\nclutter everything up with many separate git-svn repos.\n\nExample structure:\n\nclass/\n.......... systems/\n.......... algorithms/\n.......... physics/\n\nclass is one central git repository, and systems, algorithms, and\nphysics contain data from three svn repositories.  Ideally, you could\ncommit/update to/from each svn repo individually, or all at once.\n\nTim\n"},{"id":"97068","messageId":"49369066.7030101@drmicha.warpmail.net","threadId":"16564","inReplyTo":"4753154c0812021222t2886f986id2b775f90d4ea7f@mail.gmail.com","subject":"Re: Multiple SVN Repos Inside A Git Repo","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2008-12-03T13:57:58Z","receivedAt":"2008-12-03T13:57:58Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Tim Sally venit, vidit, dixit 02.12.2008 21:22:\n> Using git-svn, it is possible to have different parts of a git repo\n> correspond to a specific svn repo? From my understanding after reading\n> the documentation, you need one git repository per svn.  My example is\n> that I'm trying to set up a git repo to version control everything\n> from my classes, but each class has a separate svn repo.  Also, the\n> number of git repos I can create is limited, and I'd rather not\n> clutter everything up with many separate git-svn repos.\n> \n> Example structure:\n> \n> class/\n> .......... systems/\n> .......... algorithms/\n> .......... physics/\n> \n> class is one central git repository, and systems, algorithms, and\n> physics contain data from three svn repositories.  Ideally, you could\n> commit/update to/from each svn repo individually, or all at once.\n> \n> Tim\n\nYou can have as many git svn configurations in a single git repo as you\nwant (see the \"-R\" argument to git svn). They will all correspond to\ndifferent remote branches. By checking out the branches (or a\ncorresponding tracking branch) you can switch between the branches, i.e.\nbetween classes.\n\nI don't think a layout as above is possible given your requirements that\n- you (basically) want a single git repo and\n- you want to be able to commit back.\nThey exclude using submodules resp. subtree merge.\n\nMichael\n"}]}