On Thursday, August 19, 2010 05:31:35 pm Thomas Zander wrote: > On Thursday 19. August 2010 18.00.32 Matt Williams wrote: > > I would say that in this situation, they're a good candidate for > > splitting out into a separate module called kdebindings-support or > > even moving into kdesupport itself. This is, however, completely > > orthogonal to the Git migration. > > Yes, this looks like it is. > > Richard and Arno; would it make sense to do the above strategy in svn > right now? > Doing it at the same time as a git migration is possible; but if some code > or build setup has to be changed to make stuff compile again that sounds > like a recipy for pain to do at the same time. > > If you don't want some parts of kdebindings to be part of the big KDE > software collection, then the above strategy makes total sense to me. I want people to be able to do peer to peer development using the capabilities of git. I want there to be a one-to-one correspondence between a project which people want to maintain outside of the kde git repo, and the kde git repo version. The QtRuby project in github needs to be a clone of the kde git repo project.
I'm not exactly sure what this kdebindings-support module would be. If it is an arbitrary jumble of qt-only things and tool things, then it won't fly in the git distributed peer-to-peer repo world that we want have. -- Richard _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
