Hi all

 From my point of view I did not get a clear answer to my question. How 
do you think
we should proceed. Now I'm stuck: working in 3.5 and producing a lot of 
changesets that will not load in 3.6,
spending time to remove the change related to the removed classes.....I 
still think that wer are doing too much
at the same time. If I have one hour to clean the kernel, I do not have 
one hour to fix the changesets I already produced and fix the kernel.

So I will try to find some time to play with conflictchecker but again 
I will not be cleaning.

I agree with tim, I would like to arrive fast to a core that is stable 
and I would like to focus on that and push the other guys here to help.

Stef



On Wednesday, June 4, 2003, at 10:57 AM, <diegogomezdeck at consultar.com> 
wrote:

> Tim, Stef,
>
>>> We suffered exactly the same problem with MCP and we "solve" it with
>>> scripts that get the list of removed classes (from the changesets) 
>>> and
>>> we create a second changeset with the modifications we made to the
>>> removed- stuff.
>>
>> Sounds an interesting approach - tell us more!
>
> It is nothing special.  I only asked the changeset for the list of 
> removed
> classes and (using this collection of removed-classes) I moved all of 
> them
> to another ChangeSet.
>
> I revived the scripts we used in: 
> http://minnow.cc.gatech.edu/squeak/3205
>
> Cheers,
>
> Diego
>
>
>
>