Reinier:

Actually, these change sets are not filing in:  #methodsFor:stamp: not
understood.  Do I need to update something else, first?


Anyone:

Why do we create a partially filed-in change set?  Can we give the user an
option to remove the incomplete change set at point of file-in error?

I'm trying to rapidly survey the entire class hierarchy.  I really need an
collapsible tree view to do this efficiently, even with multiple browsers
up.  Has anyone written such a view?