{"thread":{"id":"25126","subject":"git-svn, git-submodule, and svn externals","startedAt":"2010-09-17T05:28:44Z","lastAt":"2010-09-17T05:28:44Z","messageCount":1,"participants":["Chris Frey"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"150865","messageId":"20100917052844.GA13321@foursquare.net","threadId":"25126","inReplyTo":null,"subject":"git-svn, git-submodule, and svn externals","fromName":"Chris Frey","fromEmail":"cdfrey@foursquare.net","sentAt":"2010-09-17T05:28:44Z","receivedAt":"2010-09-17T05:28:44Z","isPatch":false,"sender":{"key":"cdfrey@foursquare.net","avatar":null},"body":"Hi,\n\nI'm struggling to find a clean way to manage a SVN project in git.\nThis SVN project consists of a library, an app, and numerous plugins.\nEach of these has its own svn repo.  Each repo has an external\nwith common build checks.\n\n1) I'd like to find a way to track one svn project, including its\n\texternal, and be able to dcommit to it without worrying about\n\tthe submodule commit.\n\n\tRight now I have a git repo that tracks the svn external\n\tand a repo that tracks, for example, the library.\n\tI combine them with git-submodule, and therefore have a\n\tcommit in the tree for the .gitmodule file and submodule\n\tdirectory.\n\n\tEach time I want to git svn dcommit, I create a new branch,\n\trebase it onto master without the .gitmodule commit, and\n\tdcommit.  There's gotta be a better way.\n\n2) Ideally, I would like to combine the library and all the modules\n\tin a single git repo that I can type 'make' at the root and\n\tbuild everything.  It would be nice if I could do development\n\tin this meta tree, and commit to each various separate repo.\n\tThe commits eventually have to make their way back to their\n\tseparate SVN repos.\n\n3) I'd like to share my git repo, so that people who want to use git,\n\tcan use git, and not have to futz about with tracking SVN.\n\n\nWhat technology springs to mind when you read these requirements? :-)\n\nThanks in advance,\n- Chris\n"}]}