Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!mimsy!nocusuhs!nmrdc1!rdc30
From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: news.software.b
Subject: Re: warning to all sinners in regard to current C News patches
Message-ID: <1991Mar28.200354.12189@nmrdc1.nmrdc.nnmc.navy.mil>
Date: 28 Mar 91 20:03:54 GMT
References: <1991Mar27.152155.27218@nmrdc1.nmrdc.nnmc.navy.mil> <1991Mar27.165259.28073@nmrdc1.nmrdc.nnmc.navy.mil> <1991Mar27.185851.9247@zoo.toronto.edu>
Organization: Naval Medical Research & Development Command
Lines: 21

In article <1991Mar27.185851.9247@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>In article <1991Mar27.165259.28073@nmrdc1.nmrdc.nnmc.navy.mil> rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) writes:
>>I just noticed that C-News itself does not generate RFC822/1036 compliant dates
>>because it uses the form:
>>
>>	Wdy Mon DD HH:MM:SS YYYY
>>
>>at least that is what's in the Date: field of several articles I just posted.
>
>I think you may need to investigate your copy of C News, because that's not
>what it's supposed to be supplying, if it's current.  The current version

I discovered almost immediately after I posted that it was the reader (trn)
displaying the date in ctime(3) format.  Using the verbose command, the
proper date format was there.  I cancelled the article but I guess not
fast enough, sigh.
-- 
Mike Dobson, Sys Admin for      | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.2     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2                 | MCI-Mail: 377-2719 or 0003772719@mcimail.com