Excerpts from Dimitris Chloupis's message of 2015-12-07 08:24:13 +0100:
> > well, i wouldn't need or even want it in memory, so on disk is fine. the
> > problem is more likely management of the same. browsing the changes is not
> > really convenient.

> There are versions already for methods. So the functionality is there.

only if i save them in monticello though, and i can't just switch the version
of a single method, only the whole changeset at once. in git i can limit
browsing to a specific file, and then copy an old version of a file into the
current workspace. it is a bit crude, but it can be done. i don't see that kind
of functionality in pharo. the data is there, but the tools to use the data in
this specific manner are not.