These messages (your entire thread) are being routed to sco.com. Would you please contact you email administrator (postmaster) to resolve this ... mha@sco.com

From netadm Wed Oct 2 13:31:08 1996 Message-Id: <199610022006.PAA18054@ector.cs.purdue.edu> Cc: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A.\ Chernov) <ache@nagual.ru> To: tz@elsie.nci.nih.gov Subject: Re: Russia autumn 1996 DST patch In-Reply-To: Your message of "Wed, 02 Oct 1996 14:23:10 +0400." <199610021023.OAA00834@nagual.ru> Date: Wed, 02 Oct 1996 15:06:06 -0500 From: "Markus G. Kuhn" <kuhn@cs.purdue.edu>

In message <199610021023.OAA00834@nagual.ru>, Andrey A. Chernov wrote:

...

Why you not try to change GMT to something else? Assume that this idea becomes reality and you understand my complaints. MSK/MSD sounds here like GMT for you.

Actually, I *do* suggest to change all occurances of the string GMT in tzdata to UTC, the correct modern term. Reasonable exceptions are only comment text references to historic time zones before 1972 (when UTC replaced GMT as the reference time and GMT was redefined and replaced by the term UT1) and where the term GMT is necessary for backwards compatibility.

UTC is the official term even in the U.S. now (according to USNO folks since 1986). If you listen with your shortwave radio to WWV (2.5, 5, 10, or 15 MHz), the U.S. NIST time announcement broadcast says: "At the tone ... twenty-three hours ... fifty-nine minutes ... coordinated universal time ... beep".

Markus

-- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn@cs.purdue.edu ================================================================================ Michael H. Auria mha@sco.com Santa Cruz Operation Information Services Communications Group Account/Alias/Remote Access Administrator Smith & Wesson: the original point & click interface ... (408) 429-4501