On Mon, 5 Apr 2010, Chris Muller wrote:

>>> Well, I'm talking about the case where it is accepted, not rejected.
>>> It becomes part of the MC model's ancestry and therefore it needs to
>>> be in the trunk if we want to enable MC's functionality of diffing
>>> between versions; don't we?
>>
>> I thought you were talking about some sort of automatic copying when the
>> package is moved to the Treated Inbox.
>
> My main goal is to avoid MC's confusing unhandled error that occurs
> when a version that is part of the ancestry is not in the trunk
> repository, and I try to diff with that version.
>
> Whether that is an automatic or manual process, we should do it.

Okay, I was trying to point out that it wouldn't work automatically. But 
we don't need a copy at all, just move the package to the Trunk instead 
of the Treated Inbox after the merge.


Levente

>
> Shouldn't packages in the inbox that were merged directly into the
> trunk be moved to the trunk rather than the treated project?  That
> way, the real Squeak has a full and complete history and accounting,
> and allowing MC to work..
>