Okay there is now a branch with this and the trunk has been reverted.

Sorry I did not intend to check this in yet but I needed to get the 
changes off a Windows machine that was being used to develop it.

Now that I know how to make a branch (thanks for those scripts!) I can 
try to do this correctly. I never figured out why svn thinks you have to 
remember the revision numbers, but your script makes them be stored so 
that "merge all the changes since I did it last time" is the simple 
operation it should be. And because the numbers can be directly altered, 
I was able to revert the trunk and make the branch think it branched 
from that trunk version.

Michael Sweet wrote:
> [email protected] wrote:
>> Author: spitzak
>> Date: 2007-05-13 17:58:07 -0400 (Sun, 13 May 2007)
>> New Revision: 5821
>> Log:
>> Made the base widget class have children widgets, rather than the Group
>> subclass. This is similar to GTK and should remove a number of kludges
>> and rtti tests, and allow buttons and other widgets to be decorated
>> with child widgets.. Some code needs to be fixed as Widget::parent() 
>> returns
>> a Widget* rather than a Group*.
>>
>> This is still a work in progress, as the basic Widget does draw or do
>> anything with it's children, and several widgets such as menus are
>> still subclasses of Group rather than of Widget.
> 
> Bill, I'm going to be blunt here: MAKE A FUCKING BRANCH FOR DISRUPTIVE
> CHANGES YOU AREN'T FINISHING IN A SINGLE COMMIT.  It is trivial to do,
> you can even use some simple shell scripts I've created for this at:
> 
>     http://www.easysw.com/~mike/svn-cheat.html
> 
> Breaking things in trunk just pisses people off, and trunk is already
> unstable enough as it is...
> 
> Thank you!
> 
> PS: I'm not saying that I don't welcome these changes, but I'd
> welcome a complete changeover more than a partial commit that by
> your own admission won't compile...
> 
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to