On 8 May 2013 13:53, Frank Shearar <frank.shearar at gmail.com> wrote:
> On 8 May 2013 13:30, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>
>> On 2013-05-08, at 14:21, Frank Shearar <frank.shearar at gmail.com> wrote:
>>
>>> On 8 May 2013 06:53, Frank Shearar <frank.shearar at gmail.com> wrote:
>>>> On 7 May 2013 22:38, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>>>>
>>>>> On 2013-05-07, at 21:07, commits at source.squeak.org wrote:
>>>>>
>>>>>> Bert Freudenberg uploaded a new version of MonticelloConfigurations to project The Trunk:
>>>>>> http://source.squeak.org/trunk/MonticelloConfigurations-bf.112.mcz
>>>>>>
>>>>>> ==================== Summary ====================
>>>>>>
>>>>>> Name: MonticelloConfigurations-bf.112
>>>>>> Author: bf
>>>>>> Time: 4 May 2013, 8:19:17.367 pm
>>>>>> UUID: 3b23e53c-ca6e-47af-b3a1-12a73857fc22
>>>>>> Ancestors: MonticelloConfigurations-fbs.111
>>>>>>
>>>>>> Allow moving methods and classes between packages independent of their order in the configuration.
>>>>>
>>>>>
>>>>> This has been sitting in the inbox for a couple of days. It's working fine for me so I decided to push it.
>>>>>
>>>>> Now Frank should be able to move stuff freely between packages :)
>>>>>
>>>>> Note this *only* affects things reorganized, the config map is still important for other kinds of order dependencies.
>>>>
>>>> Thanks very much, Bert!
>>>
>>> Hm, I think we need one more map update? bf.235 has Monticello loading
>>> before MonticelloConfigurations, and that means that you get an MNU in
>>> MCConfiguration >> #preloadMovesBetween: because
>>> MCReorganizationPreloader is an unknown class...
>>>
>>> frank
>>
>>
>> Err, of course, I meant to include both, Monticello  and MonticelloConfigurations ... Fixed now.
>
> It's not all bad - it revealed a bug in my CommandLineToolSet, where I
> dumped the wrong context to stdout.
>
> Thanks!

Er, so just because I'm having a slow day, should I push out a new
config map every time I shuffle methods around?

frank

> frank
>
>> - Bert -
>>
>>
>>