<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>> <span style="font-size:12pt">Well, maybe not so effective after all, given that the commit notice </span><span style="font-size:12pt">for Monticello-dtl.727 on the mailing list still exhibits the same problem.</span></p>
<div><br>
</div>
<div>Isn't that notice generated by some servers that depend on a Trunk image rather than the uploaded inbox version itself?</div>
<div><br>
</div>
<div>Best,</div>
<div>Christoph</div>
<p></p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div><font size="2" color="#808080"></font></div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von David T. Lewis <lewis@mail.msen.com><br>
<b>Gesendet:</b> Dienstag, 8. September 2020 01:59:00<br>
<b>An:</b> The general-purpose Squeak developers list<br>
<b>Betreff:</b> Re: [squeak-dev] Recent Monticello Timestamps</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Well, maybe not so effective after all, given that the commit notice<br>
for Monticello-dtl.727 on the mailing list still exhibits the same problem.<br>
<br>
Dave<br>
<br>
On Mon, Sep 07, 2020 at 07:52:02PM -0400, David T. Lewis wrote:<br>
> A crude but effective fix is in the inbox in Monticello-dtl.727<br>
> <br>
> Dave<br>
> <br>
> On Mon, Sep 07, 2020 at 03:56:19AM +0200, Levente Uzonyi wrote:<br>
> > Hi Eliot,<br>
> > <br>
> > <br>
> > The Monticello history of the Chronology package says that <br>
> > those microseconds were introduced by Kernel-eem.970:<br>
> > <br>
> > >Changes to Time and Delay prior to changing over to the utc microsecond <br>
> > >clock and its use in delay scheduling.<br>
> > <br>
> > The "offending" change is probably the following:<br>
> > <br>
> > Item was changed:<br>
> > ----- Method: Time class>>now (in category 'ansi protocol') -----<br>
> > now<br>
> > "Answer a Time representing the time right now - this is a 24 hour <br>
> > clock."<br>
> > + | localUsecs localUsecsToday |<br>
> > + localUsecs := self localMicrosecondClock.<br>
> > + localUsecsToday := localUsecs \\ MicrosecondsInDay.<br>
> > + ^ self<br>
> > + seconds: localUsecsToday // 1000000<br>
> > + nanoSeconds: localUsecsToday \\ 1000000 * 1000!<br>
> > -<br>
> > - | ms |<br>
> > -<br>
> > - ms := self milliSecondsSinceMidnight.<br>
> > -<br>
> > - ^ self seconds: (ms // 1000) nanoSeconds: (ms \\ 1000) * 1000000<br>
> > -<br>
> > -<br>
> > - !<br>
> > <br>
> > And that happened more than four and a half years ago.<br>
> > <br>
> > <br>
> > Levente<br>
> > <br>
> > On Sun, 6 Sep 2020, Eliot Miranda wrote:<br>
> > <br>
> > >Name: VMMaker.oscog-eem.2800<br>
> > >Author: eem<br>
> > >Time: 6 September 2020, 4:58:47.598839 pm<br>
> > >UUID: a6116113-df13-435d-968d-e9b111676754<br>
> > >Ancestors: VMMaker.oscog-eem.2799<br>
> > ><br>
> > >Seriously ?!??! ;-)<br>
> > >_,,,^..^,,,_<br>
> > >best,??Eliot<br>
> > ><br>
> > ><br>
> <br>
> > <br>
> <br>
> <br>
<br>
</div>
</span></font>
</body>
</html>