On Sun, Feb 6, 2011 at 4:07 AM, Miklos Vajna <vmik...@frugalware.org> wrote: > On Mon, Jan 31, 2011 at 03:39:41PM +0100, Jan Holesovsky <ke...@suse.cz> > wrote: >> Can you please do a bit of research in that regard, and summarize how we >> would gain from using git submobule? > > To my understanding, in short: > > Con: build.git has to be updated manually (it has to be decided how > frequently), ideally after every 'g push', but that would cause a lot of > "bogus" commits in build.git, which sounds ugly. humm... what build.git ? :-) on master I do not even clone build.git anymore...
> Con: it seriously increase the barrier of entry. git already scare some people... git + submodule at that scale will be much worse Con: it would be using submodule in a way it was certainly not intended to be used. That means that doc and support for that will be scarse and chance of screwing things up rise big time, with very few 'expert' - if any - to sort things out. Con: how well is it going to mesh with the fact that some git repo are 'optional' (l10n) ? Con: that will probably mess with the hg import script. we would need to make sure that import is still feasible - without breaking the current history Note that the main drawback of our current approach is indeed the bisection problem. It would be certainly be convinient to be able to bisect on the entire set of repos... but how much pain/risk do we want to take to improve that aspect of things ? Norbert > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > > _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
