From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Subject: Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch))
Date: 13 May 1996 23:41:08 -0500 [thread overview]
Message-ID: <ufa4tpjhnob.fsf_-_@sina.hpc.uh.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 11 May 1996 02:37:06 +0200
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
LMI> Steven L Baur <steve@miranova.com> writes:
>> If this Subject: were instead: Subject: Re: Re[2]: Re^3: [hwg-main] Web
>> site -Reply -Reply -Reply
>>
>> What would the harm be in Gnus rewriting the header as: Subject: Re:
>> [hwg-main] Web site
LMI> That would violate the GNKSA. Even if that were not the case,
LMI> rewriting subject headers will break threading (and stuff) on some
LMI> newsreaders.
I will always rewrite the subject of a message to be both pertinent and
devoid of Re: RE^8: Re[356]: -Reply garbage. If there are newsreaders that
can't understand it then tough. The subject line is for humans. A
newsreader should be looking at References: (or In-reply-To: which we don't
seem to set). IMHO, of course.
- J<
next prev parent reply other threads:[~1996-05-14 4:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-09 18:21 [sgnus v0.83] Followup Subject: typos in message.el (patch) Steven L Baur
1996-05-09 21:58 ` Lars Magne Ingebrigtsen
1996-05-10 1:50 ` Raja R Harinath
1996-05-10 3:29 ` Steven L Baur
1996-05-11 0:37 ` Lars Magne Ingebrigtsen
1996-05-14 4:41 ` Jason L Tibbitts III [this message]
1996-05-14 12:25 ` Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch)) Per Abrahamsen
1996-05-14 14:32 ` Richard Pieri
1996-05-14 15:25 ` Per Abrahamsen
1996-05-14 17:28 ` Richard Pieri
1996-05-14 18:44 ` Sudish Joseph
1996-05-15 2:07 ` Lars Magne Ingebrigtsen
1996-05-15 4:31 ` Greg Stark
1996-05-15 14:10 ` Sudish Joseph
1996-05-15 21:53 ` Edward J. Sabol
1996-05-15 22:25 ` Steven L Baur
1996-05-15 3:15 ` Greg Stark
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=ufa4tpjhnob.fsf_-_@sina.hpc.uh.edu \
--to=tibbs@hpc.uh.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).