On Fri, May 21, 2010 at 12:33:19PM -0500, Rob Savoye wrote: > On 05/21/2010 11:33 AM, Benjamin Wolsey wrote: > > > If there is one more such commit, I will start to maintain my own stable > > branch of Gnash elsewhere and do future work there until the maintenance > > of Gnash trunk changes. > > As I sit here fixing breakage caused by your own checkin, I find it > hard to have compassion.
C'mon rob, I'm not working on the codebase right now but I've heard this argument from you so many times that my blood pressure raises as well here. If your commits badly break things you should take immediate action to fix, or revert if you don't have time. Failing to do so forces other to do it and if your local repository breaks due to that it's not as important as breaking the shared one. > The usual policy of free software projects is > frequent checkins are good. Yes, but I'd add "small" and most important "not breaking the testsuite". > In a large team project we're supposed to > help each other achieve the common goal I agree, so what about trying to figure out what's wrong with your runs of 'make check' failing to detect troubles ? --strk; () Free GIS & Flash consultant/developer /\ http://strk.keybit.net/services.html _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
