Why multiple change files?

Avi Bryant avi at beta4.com
Sun Mar 7 21:45:25 UTC 2004


On Mar 9, 2004, at 8:54 AM, Lex Spoon wrote:

> 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.

Yes, it certainly can.  With all of my source managed by Monticello, 
images have become largely throwaway for me - any time I feel like I'm 
getting too many images, I go through them all to make sure I've 
committed whatever modifications they have to an appropriate branch, 
and then delete them en masse.  It's very easy to start from a fresh 
image and load in the right packages again.

This wouldn't work as well if you had a lot of non-code content, of 
course.




More information about the Squeak-dev mailing list