Just adding some thoughts/views here to strenghten what Thiago said. On Monday 5. May 2008 10:31:53 Thiago Macieira wrote: > I agree with Johannes here. I know Oswald wants the split at the > library/app level inside the KDE main modules. But I don't think > Git-submodule support is good enough for that purpose (I don't think it > will ever be, since it's not the objective). That is, it doesn't feel like > a single, unique repository.
More importantly, there is no need to split up that much. I've been amazed at the speed of git many times, the whole of KOffice (160Mb checkout) can be added from scratch to git in < 20 seconds using git add. Doing diffs, commits etc all take equally short amount of time. This, to me, means that there really is little use in splitting up; its not subversion which takes forever to do something... > Definitely not for kdelibs, kdepimlibs, kdebase, kdepim, which are very > tightly-integrated modules. (In fact, given the current level of > cross-repository copy/move support in Git, I'd be tempted to lump kdelibs > and kdebase together) Some of the others may work, though. Agreed, the point of having one repo is that your commits stay atomic. You throw that out the window if you split up too much. So if you see people commit across subdirs this means those subdirs should stay in one module. This effectively means (to me) that KOffice should stay one module too. And since even KDEGames has a library, I don't think you can split up too many other places either as a commit in the libs dir typically means a change in the apps dirs that really should belong to the same changeset. Cheers! -- Thomas Zander
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
