On Wed, Oct 1, 2014 at 12:29 PM, Oliver Lietz <[email protected]> wrote: > On Wednesday 01 October 2014 17:25:50 Carsten Ziegeler wrote: >> I'm not against moving to git, but the number one criteria would be to have >> a git repository per module. > > To be honest, that is not a criteria.
I'll rephase Carsten's assertion slightly differently - we need a repository per release unit. So for our purposes, this is mostly one per module, but not necessarily always (Launchpad, for example). > I also don't like one big repo (yet), > but what problem(s) should one repo per module solve (we would than have > between 200 and 300 repos)? > > I don't like to have the complete project source under a module's tag but the > way it is now on GitHub where a tag for a module only contains that module. > Is it that what you want to get from one repo per module? I want to be able to diff a tag against master and get something coherent. That can IMHO only happen if you have a repository per release unit. > > Checking out/clone a complete big repo shouldn't be expensive - or several > like bundles, contrib, installer, launchpad, parent, performance, samples, > site, testing, tooling (which makes it harder to move modules between bundles > and contrib but this is a different story). There are a variety of solutions to this. Git Slave seems to be working well enough. Regards, Justin > > O. > >> Carsten >> >> 2014-10-01 16:00 GMT+02:00 Oliver Lietz <[email protected]>: >> > Please discuss on list and add your findings to the wiki: >> > >> > >> > https://cwiki.apache.org/confluence/display/SLING/Move+from+Subversion+to >> > +Git >> > >> > Thanks, >> > O.
