Smalltalk › Pharo › Pharo Smalltalk Developers

Can we rollback the MC changes?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

stepharo

Can we rollback the MC changes?

Hi

I strongly encourage that we rollback the change in MC that broke the
ancestry.
This enhancement really breaks MC and makes quite difficult to work with
it.
How should we proceed?

Stef

PS: do not tell me that this is working.

stepharo

Re: Can we rollback the MC changes?

If you want to see how deep it is broken

take
Latest update: #50063
open rubric repo merge alain 206
and see that we lost all the feedback on merged ancestor.

So to merge now I will click on all the files to make sure.
Great!

Stef

Le 25/5/15 10:43, stepharo a écrit :

> Hi
>
> I strongly encourage that we rollback the change in MC that broke the
> ancestry.
> This enhancement really breaks MC and makes quite difficult to work
> with it.
> How should we proceed?
>
> Stef
>
> PS: do not tell me that this is working.
>
>
>

Thierry Goubier

Re: Can we rollback the MC changes?

In reply to this post by stepharo

Hi Stef,

this is probably the lazy ancestor thing, but, as long as nobody looks
seriously into why this happens, then we can't be sure (I just suspect
it is a side effect of that).

To remove it, it's easy:

remove MCLazyVersionInfo.

revert the effect of MCLazyVersionInfo>>install.

Regards,

Thierry

Le 25/05/2015 10:43, stepharo a écrit :

> Hi
>
> I strongly encourage that we rollback the change in MC that broke the
> ancestry.
> This enhancement really breaks MC and makes quite difficult to work with
> it.
> How should we proceed?
>
> Stef
>
> PS: do not tell me that this is working.
>
>
>

stepharo

Re: Can we rollback the MC changes?

Thanks.
Esteban told me that he should look at it. Now I think that the change
arrived too late in the process.

Stef

Le 25/5/15 11:21, Thierry Goubier a écrit :

> Hi Stef,
>
> this is probably the lazy ancestor thing, but, as long as nobody looks
> seriously into why this happens, then we can't be sure (I just suspect
> it is a side effect of that).
>
> To remove it, it's easy:
>
> remove MCLazyVersionInfo.
>
> revert the effect of MCLazyVersionInfo>>install.
>
> Regards,
>
> Thierry
>
> Le 25/05/2015 10:43, stepharo a écrit :
>> Hi
>>
>> I strongly encourage that we rollback the change in MC that broke the
>> ancestry.
>> This enhancement really breaks MC and makes quite difficult to work with
>> it.
>> How should we proceed?
>>
>> Stef
>>
>> PS: do not tell me that this is working.
>>
>>
>>
>
>
>