{"thread":{"id":"23440","subject":"SVN bridge for multiple SVN modules","startedAt":"2010-04-13T07:34:14Z","lastAt":"2010-04-14T12:43:15Z","messageCount":3,"participants":["Richard Dallaway","Steven Michalske"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"139396","messageId":"m2ue3041f5c1004130034h51eb196dke0ebb8b3634e7302@mail.gmail.com","threadId":"23440","inReplyTo":null,"subject":"SVN bridge for multiple SVN modules","fromName":"Richard Dallaway","fromEmail":"dallaway@gmail.com","sentAt":"2010-04-13T07:34:14Z","receivedAt":"2010-04-13T07:34:14Z","isPatch":false,"sender":{"key":"dallaway@gmail.com","avatar":null},"body":"Hello\n\nWe've run into something we'd like to do with \"git svn clone\" that\nlooks like it should work, but doesn't appear to.\n\nThe task: we have an SVN repository with 38 modules in it (each with\ntheir own branches, tags, and trunk) and we'd like to pull just two of\nthe modules into a single git repository -- but maintain the ability\nto perform git svn rebase/fetch/dcommit as the SVN repository is\nremaining active for some developers.\n\nIt looks like we should be able to point at the parent of the SVN\nmodules and use --ignore-paths=/a long regexp/  to do the job, but\nwe've not managed to get it to work yet and we're now wondering if\nwe're missing a few concepts in the git/svn bridging concepts. Or\nmaybe we've just not got the syntax right yet.\n\nThere's a related question we spotted on stackoverflow that indicates\nthis isn't possible:\n\nhttp://stackoverflow.com/questions/898568/multiple-svn-projects-into-one-git-repository\n\nIf that is the case (can anyone confirm?), is there a way we can do\nthis by pulling each SVN module into a separate intermediate git\nrepository, then doing \"something\" to push on to our target single\nrepository.... a \"something\" that would still enable us to git svn\nfetch and git svn dcommit back to the SVN repo?\n\nSuggestions, clues, explanations all very welcome.\n\nRegards\nRichard\n"},{"id":"139454","messageId":"236FD58B-CE33-4C06-A3AC-FD7DA7593EEB@gmail.com","threadId":"23440","inReplyTo":"m2ue3041f5c1004130034h51eb196dke0ebb8b3634e7302@mail.gmail.com","subject":"Re: SVN bridge for multiple SVN modules","fromName":"Steven Michalske","fromEmail":"smichalske@gmail.com","sentAt":"2010-04-14T06:08:05Z","receivedAt":"2010-04-14T06:08:05Z","isPatch":false,"sender":{"key":"smichalske@gmail.com","avatar":"https://gravatar.com/avatar/721f27456adc9ac84f3bb235f021a70015abb9e09222ae8622fc5579c6a203c1?d=mp&s=160"},"body":"On Apr 13, 2010, at 12:34 AM, Richard Dallaway wrote:\n> Hello\n>\n> We've run into something we'd like to do with \"git svn clone\" that\n> looks like it should work, but doesn't appear to.\n>\n> The task: we have an SVN repository with 38 modules in it (each with\n> their own branches, tags, and trunk) and we'd like to pull just two of\n> the modules into a single git repository -- but maintain the ability\n> to perform git svn rebase/fetch/dcommit as the SVN repository is\n> remaining active for some developers.\n>\nWould setting up two git repositories cloning the SVN from the  \nmodule_a and module_b directories and then making them as a git  \nsubmodules is a git super project repository?\n"},{"id":"139470","messageId":"v2ye3041f5c1004140543w11a16b48ye3095b266c0bc9b1@mail.gmail.com","threadId":"23440","inReplyTo":"236FD58B-CE33-4C06-A3AC-FD7DA7593EEB@gmail.com","subject":"Re: SVN bridge for multiple SVN modules","fromName":"Richard Dallaway","fromEmail":"dallaway@gmail.com","sentAt":"2010-04-14T12:43:15Z","receivedAt":"2010-04-14T12:43:15Z","isPatch":false,"sender":{"key":"dallaway@gmail.com","avatar":null},"body":"On Wed, Apr 14, 2010 at 7:08 AM, Steven Michalske <smichalske@gmail.com> wrote:\n> On Apr 13, 2010, at 12:34 AM, Richard Dallaway wrote:\n> Would setting up two git repositories cloning the SVN from the module_a and\n> module_b directories and then making them as a git submodules is a git super\n> project repository?\n\nThank you - I'll take a look at that.\n\nI'm surprised that the \"git svn clone\n--ignore-paths=/everything_except_the_two_I-Want/\" doesn't solve the\nproblem: I don't understand why it doesn't, and would love to\nunderstand this better if anyone has a way to explain it.\n\nCheers\nRichard\n"}]}