Why multiple change files?

Lex Spoon lex at cc.gatech.edu
Tue Mar 9 16:54:51 UTC 2004


That seems odd to me to mainain 30 different snapshots into the history
of your project.  It would seem that a proper code versioning system
could do much better.  So yes, your style sounds erratic to me.  :)

Now, you can use most any change sets mechanism to make *code* snapshots
and return to them.  Monticello should work fine, for example.  Also, I
expect that Monticello would support branching code versions, but I
don't know for sure.

For the record, Squeak's method and changes files work the way you
describe, and it should be possible to make multiple images use the same
changes file.

I don't know what the UI for sharing changes files should be, however. 
In fact, the idea mildly bothers me, because it complicates an
already-complicated model.  I would like to move in the other direction,
and not have the changes file appear to the user at all.  I'd rather we
had some sort of "snapshot" file which included both image and a changes
log.


-Lex



More information about the Squeak-dev mailing list