Why do ChangeSets sort?

torge.husfeldt at gmx.de torge.husfeldt at gmx.de
Mon Feb 24 16:54:06 UTC 2003

Hi Lex,

"Lex Spoon" <lex at cc.gatech.edu> wrote:
> "Richard A. O'Keefe" <ok at cs.otago.ac.nz> wrote:
> That said, I do feel your pain.  :)  If you look at the list of
> changesets for Islands, you'll see a lot of things like foo1.cs,
> foo2.cs, foo3,cs, where I manually separated a sequence of changes into
> separate changesets.  It's a special pain when later versions of the
> changeset rewrite methods that are in earlier ones, because if I file
> them back *out* again it will use the "new" version.  Arg!  Still,
This doesn't have to be that way!
Every ChangeRecord knows it's currentMethod and can easily detect
when it is out of sync. I've planned for a long time to write a
that adds such a check to the #hasSlips but didn't yet come around to
really doing it.

> compared to the effort of *finding* a good sequence of changes,
> separating the changes into separate changesets is nothing.

> Lex

More information about the Squeak-dev mailing list