On Tue, Sep 20, 2011 at 12:50 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
yes please send it.
How do you determine ancestry?

Here's the phrase:

ChangeSet directAncestryOfVersions: (ChangeSet
scanVersionsOf: method�
class: self�
meta: self isMeta
category: category�
selector: selector)

the scanVersionsOf: is standard, and then I added�directAncestryOfVersions: to filter appropriately.


Find attached. �You'll need to understand it, test it and integrate it, but it worked fine for me. �I haven't had time or occasion to push it to Squeak trunk. �But if people like it I'll think about doing so. �I agree with Henrik that this is a useful default. �I love method versions, and noise is noise, so this is having one's cake and eating it too :)

Enjoy!

Stef

On Sep 20, 2011, at 9:32 PM, Eliot Miranda wrote:

>
>
> On Tue, Sep 20, 2011 at 5:53 AM, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote:
> On 20.09.2011 14:49, Marcus Denker wrote:
> Hi,
>
> The .changes have gotten really large... (32MB...)
>
> So I will do a condense in the next update.
>
> NOTE: this will take quite some time to finish, so maybe wait for a pre-built image or Jenkins...
>
> � � � �Marcus
>
>
> --
> Marcus Denker -- http://marcusdenker.de
>
>
> Noooooooooo, please please don't...
> Method history is so much more useful than 20 extra MB's on my HD :S
>
> This is /not/ a dichotomy. �For my image I wrote a condenseSources that preserves history. �It edits out duplicates, and cuts off branches in the history that lead nowhere. �So at the end you get all the versions of each method that are ancestors of the current version. �I can email you the code and you could consider making it the default. �Let me know.
>
>
> Cheers,
> Henry
>
>
>
>
> --
> best,
> Eliot
>





--
best,
Eliot