On 3 November 2011 17:16, Max Leske <[email protected]> wrote: > :-D > I said: "In MY opinion" > > Ok, so the .changes file serves as a backup. But shouldn't the file be > optional? e.g. the source code is in the image and changes are backed up to > an extra file to guard against crashes. But I think, the image should not > depend on that file. > Does this make more sense? > It is.
> Max > > > On 03.11.2011, at 16:12, Sean P. DeNigris wrote: > >> >> Frank Shearar-3 wrote: >>> >>> I'm tempted to say that if you've never had to use your .changes file >>> to recover, you're not working hard enough :) >> >> Oh my, how my *ss has been saved by the .changes file. Especially while >> doing dangerous but important things (e.g testing bleeding edge cog vms). I >> can't count the hours... >> >> -- >> View this message in context: >> http://forum.world.st/Brainstorming-on-the-roadmap-for-first-Pharo-Consortium-Engineer-tp3955399p3986256.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > > -- Best regards, Igor Stasenko.
