Re: [Pharo-users] Managing updates/patches in Pharo with Metacello

Esteban A. Maringolo wrote

I was afraid of populating the Metacello config with lots of #version21: #version211: #version212, etc.

Config classes are just the way we serialize projects. It is like reading binary :) I wouldn't contort your workflow to make them easier to read in a browser. Have you tried Versionner? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Managing-updates-patches-in-Pharo-with-Metacello-tp477... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.