On Tue, Feb 3, 2015 at 11:26 AM, Chris Cunningham <cunningham.cb at gmail.com>
wrote:

> >>I don't kno how I did this
>
> It's quite easy.  You and Levante worked off of the same ancestor and
> committed your work.  The names mean no collision.  (or, just possibly, you
> overwrote the number in the title while committing - I've done that, but
> usually with a comment instead of a number).
>
> In either case, I could see how it would cause update to be unhappy.  Was
> ul's version an ancestor of yours, or are you skipping over it?
>

Looking at the version numbers, Levente's comes first.


>
> On Tue, Feb 3, 2015 at 10:01 AM, Eliot Miranda <eliot.miranda at gmail.com>
> wrote:
>
>> Hi All,
>>
>>     I've screwed up and somehow managed to create an update with the same
>> number as a previous one.  You'll see in trunk update
>>
>> update-eem.295.mcm
>> update-ul.295.mcm
>>
>> and in update.spur
>>
>> update.spur-eem.295.mcm
>> update.spur-ul.295.mcm
>>
>> I don't kno how I did this but can some kind authorised soul rename
>> update-eem.295.mcm => update-eem.296.mcm
>> update.spur-eem.295.mcm => update.spur-eem.296.mcm
>>
>> This is playing havoc with updates...
>> --
>> best,
>> Eliot
>>
>>
>>
>>
>
>
>
>


-- 
best,
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20150203/5ab35f79/attachment.htm