Phil Martin (one of the guy behind fuel) is working on a **good** changes management because we do not like all the changes code which is old and sometimes brittle. We will have a look at your issues and see what we can do. But what is sure is that we are working on replacing all the changeset, recovery and all the rest :).
Stef On Jun 9, 2013, at 8:07 PM, [email protected] wrote: > > The interesting bit is that the crash I got occured **as I was saving to > STH**... > https://pharo.fogbugz.com/default.asp?10859#78993 > > Then Cami told me to drag & drop my .changes file inside my image to recover > the changes. > > Since was I was doing was not coding but commenting, comments were lost (and > getting into a deadly loop as well - > https://pharo.fogbugz.com/default.asp?10860#78992) > > Then looking at the Change fileIn, I noticed that thing about comments not > being taken into account: https://pharo.fogbugz.com/default.asp?10861#78994 > > So, I try to work the advertised way, I guess. > > But things is that a lot of things have the power to destroy my image it > seems. > That's why I do have a ton of large files in my working folder named like > xxxx-YYYYMMDD-HHMM.image|changes > > Still, I got burned. > > As of the old code hard to understand, sure, I got lost :-) If I would > understand what to do, instead of bugging you I'd be submitting a slice. > > Let's end this thread :-) > > Phil > > > On Sun, Jun 9, 2013 at 7:33 PM, Marcus Denker <[email protected]> wrote: > > On Jun 9, 2013, at 7:20 PM, [email protected] wrote: > > > Look, I got the point about mixing up issues. > > > > Thanks for bother to reply BTW, it is appreciated. > > > > As for > > 10861 System not filing in class comments from changes file. > > https://pharo.fogbugz.com/f/cases/10861/System-not-filing-in-class-comments-from-changes-file > > yes, this seems to be not filing in class comment from the recent changes. > > I think that nobody complained because it is not used that often and mostly > with relatively small changes > People save on SmalltalkHub very often, or saving the image before doing > something that can destroy it. > > And comments tend to be written at anther times then code that has the power > to destroy you image. > > Yes, we should fix it. And yes, the code related to all this is quite > old-style smalltalk that is hard to understand. > > Marcus >
