From: Jack Vinson <vinson@unagi.cis.upenn.edu>
Subject: Re: bug in date washing
Date: 27 Jul 1999 10:19:17 -0500 [thread overview]
Message-ID: <wkd7xep1ca.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "19 Jul 1999 13:00:44 +0200"
And when I play with Kai's message, I get the following:
Originally date header: Date: 19 Jul 1999 13:00:44 +0200
W T i Date: 19990719T130044
W T i (again) Date: 19691231T180000
W T l Date: Wed Dec 31 18:00:00 1969 --500
(clearly incorrect)
W T o Date: Wed Dec 31 18:00:00 1969 --500
(shouldn't this go back to the original?)
The only way to get back to the original date is to t'oggle the headers
twice. Many of the other gnus-summary-wash-time-map bindings don't work
very well either. If I change to elapsed time, I get the X-Sent header,
but it never changes to anything else after that.
--
Jack Vinson <jvinson@unagi.cis.upenn.edu>
Zippy: I have no actual hairline...
next prev parent reply other threads:[~1999-07-27 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-18 19:38 Paul Stevenson
1999-07-19 11:00 ` Kai Großjohann
1999-07-27 15:19 ` Jack Vinson [this message]
1999-07-26 15:34 ` Paul Stevenson
1999-08-27 20:02 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wkd7xep1ca.fsf@chevax.ecs.umass.edu \
--to=vinson@unagi.cis.upenn.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).