Interesting that this should come up the day after I managed to over-enthusiastically delete several methods ;-)

For cases where you have recently (ish) deleted something you can look at the changesorter, find the changeset currently being used (and I suspect quite a lot of people aren't really aware they even still exist after so many years of monticello) and scan for methods with 'nil' category. When yo ufind one that seems plausible select it and use 'versions' to get a list of the... versions. 'revert' the one you  want to reclaim.

For the much longer timescale situation though we need sometihng muh cleverer. Marcel's changes file scanner will help over the lifespan of a particular changes file, which I suspect will be very helpful and a lot easier than the above. For *really* log timescales though I think we need to look at the global changes log from the beginning of time (or at least, the beginning of squeak-time. I'd be delighted if we had a doit change for 'Universe goBang' at the head of the file) which is/was/could-be kept on a server somewhere. I feel sure we do in fact have a mechanism for this somewhere in the system, feel confident that Chris Muller would have had something to do with it but damned if I can find it right now. Chris? Beuller? Anyone?


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Oxymorons: Software documentation