[ENH] Better MCWorkingCopy description in PharoInbox

> Author: BernhardPieber
> Time: 21 November 2010, 6:51:13 pm
> UUID: 8ffedd96-5c55-470b-a2a0-fe81da9dd12a
> Ancestors: Monticello-StephaneDucasse.498
>
> - Changed MCWorkingCopy description so that the package name is not duplicated when, e.g. Kernel (StephaneDucasse.799) instead of Kernel (Kernel-StephaneDucasse.799). This makes the Monticello Browser easier to use.
>
> Enjoy,
> Bernhard
>
> P.S. I read http://pharo-project.org/community/issue-tracking but I am still not sure if adding an issue to the tracker is mandatory in such a case.

> thanks berhnard :)
> Nice to hear about you.
>
> Can you sign the license? :).
>
>> Author: BernhardPieber
>> Time: 21 November 2010, 6:51:13 pm
>> UUID: 8ffedd96-5c55-470b-a2a0-fe81da9dd12a
>> Ancestors: Monticello-StephaneDucasse.498
>>
>> - Changed MCWorkingCopy description so that the package name is not duplicated when, e.g. Kernel (StephaneDucasse.799) instead of Kernel (Kernel-StephaneDucasse.799). This makes the Monticello Browser easier to use.
>>
>> Enjoy,
>> Bernhard
>>
>> P.S. I read http://pharo-project.org/community/issue-tracking but I am still not sure if adding an issue to the tracker is mandatory in such a case.
>
> always!
> this is like a giant todo and integration list.
> Things that are not in there are ***lost*** not because we do it on purpose but just because
> we have busy.
>
> http://code.google.com/p/pharo/issues/detail?id=3278