From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Bug in summary buffer line?
Date: Tue, 15 Jan 2002 11:50:24 -0500 [thread overview]
Message-ID: <2n6663bltb.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <d70bejir.fsf@hschmi22.userfqdn.rz-online.de>
Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
> Niklas Morberg <niklas.morberg@axis.com> writes:
>
>>When looking at mails older than one month, the
>>`&user-date;' seems to get confused; instead of displaying
>>the date, the number of the month is displayed instead. The
>>incorrect result is this (copied from my summary buffer):
>>
>>?* okt 10 '01 [ 0 Majordomo@hpc.uh.edu] Welcome to ding
>
> Confirmed. here is the fix:
>
> --- gnus-util.el.old Sun Jan 6 15:33:04 2002
> +++ gnus-util.el Tue Jan 15 15:02:32 2002
> @@ -343,7 +343,7 @@
I'll install it.
ShengHuo
prev parent reply other threads:[~2002-01-15 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 10:02 Niklas Morberg
2002-01-15 15:11 ` Frank Schmitt
2002-01-15 15:35 ` Niklas Morberg
2002-01-15 15:52 ` Colin Marquardt
2002-01-15 16:50 ` ShengHuo ZHU [this message]
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=2n6663bltb.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.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).