On 23.09.10 14:29:53, Jason A. Donenfeld wrote: > Hello, > > Regarding the issue of managing multiple little repositories when working on > an entire module, if we decide to go with the (preferred) split approach, > has anyone considered the potential of git-submodule? I've used it for > exactly this purpose and have had a lot of success with it.
IMHO this is not (yet) suitable for our usecases. We're not talking about 1 or 2 repos that we'd put into a 'bigger' one. With each submodule that is being added to the bigger module it gets more tedious to maintain that because you have to update the bigger one each time one of the submodules is being changed. Also one has to change the remote for each subrepo you want to work on so you can push. Not to mention what happens if someone forgot to push the subrepo but pushed already the upper repo. We're using a single submodule at work to integrate a supplemental library and while it does work its also tedious and error-prone. Not really something you want to impose on first-time contributors or people not having grasped git fully yet. Andreas -- Things will be bright in P.M. A cop will shine a light in your face. _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
