Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!apple!oliveb!orc!mipos3!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: news.admin
Subject: Re: Dates in C-news
Message-ID: <1990Jan23.175245.18937@iwarp.intel.com>
Date: 23 Jan 90 17:52:45 GMT
References: <1556@fallst.UUCP> <1314@ursa-major.SPDCC.COM> <4831b2fb.bfe8@tachyon.engin.umich.edu>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 25
In-Reply-To: stealth@caen.engin.umich.edu (Mike Peltier)

In article <4831b2fb.bfe8@tachyon.engin.umich.edu>, stealth@caen (Mike Peltier) writes:
| Why was the format of the date field in the history file changed
| to a non-human-readable format?  I get the idea that it probably
| saves a bit of processor speed for the program, but it's kind of
| a pain to see a series of numbers when I want a quick and easy
| way to check the status of my newsfeed.  Any other ways to do
| this?  Thanks...

Well, they're in Nearly-Human-Readable format in the 'log' file, which
is where I'm checking on *my* newsfeeds.  And, I like the idea that
doing an expire doesn't have to parse that silly human-readable date
14 times over the two weeks that the article sits on my disk.

Besides, doesn't *everyone* know that 633117016 is
Tue Jan 23 09:50:16 1990 PST just by looking at it? :-)

(I can write you a Perl program to translate it back, if you insist.
:-)

Just another Cnews-admin,
-- 
/== Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ====\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III  |
| merlyn@iwarp.intel.com ...!uunet!iwarp.intel.com!merlyn                |
\== Cute Quote: "Welcome to Oregon... Home of the California Raisins!" ==/