--- Begin Message ---
Evan wrote:
>If anyone knows how to figure out how to force all the current good code in
>my image into one massive commit, so that other people can check out the
>current, working version, please do not hesitate to let me know.
If you are using mczs, all changes are committed each time.
Each mcz archive is a snapshot of all the classes and methods in the system
category that defines the package at the moment in time when you saved it.
Much like a git commit.
So all you need to do is to save another version of the package. Just make
sure the filename you use is unique.
If in doubt, you can use a version number that resembles a timestamp like
YourPackage-YourName.201705111236.mcz where 201705111236 is 2017-05-11,
12:36.
Best Regards,
Milan Vavra
--
View this message in context:
http://forum.world.st/Wandering-Through-Dependency-Hell-tp4946266p4946653.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
--- End Message ---
