On Sun, Mar 11, 2012 at 10:02 PM, David Faure <fa...@kde.org> wrote: > On Sunday 11 March 2012 21:27:05 Ben Cooksley wrote: >> In general, we discourage force pushing on public, published branches >> due to the problems it has been known to give those with pre-existing >> checkouts of the affected branches. Given this is a semi-private work >> branch, it should be fine in this case if needed. > > I agree. > >> Given the nature of this work, I can't help but think it might be >> better to do it in the main frameworks branch however at this point >> (many hands make light work, etc) > > I don't agree. If one unfinished frameworks breaks compilation, nobody else > can > work in the frameworks branch, on other stuff. I.e. this prevents > parallelization of the efforts. > > To be clear: widgets such as khbox can be moved one at a time without breaking > stuff. But the current kcolors frameworks (which is a bit too high-level to be > moved already, i.e. it depends on too many things that haven't moved yet) > doesn't compile, and won't for some time still.
Yes, this is what I was referring to. The kcolors material is definitely still under construction and it is too soon to move it. > > Overall I think the order in which this is happening is a bit wrong, but the > best way to realize what needs to be done is to hit the issues... :) If Giorgos/someone else wants to follow the force-push method, please file a sysadmin report and we can take care of it. > > -- > David Faure, fa...@kde.org, http://www.davidfaure.fr > Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5 > Regards, Ben _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel