From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch))
Date: 14 May 1996 17:25:07 +0200 [thread overview]
Message-ID: <rj7muf9t0s.fsf@babbage.dina.kvl.dk> (raw)
In-Reply-To: Richard Pieri's message of 14 May 1996 10:32:47 -0400
>>>>> "JLT" == Jason L Tibbitts <tibbs@hpc.uh.edu> writes:
JLT> The subject line is for humans.
>>>>> "PA" == Per Abrahamsen <abraham@dina.kvl.dk> writes:
PA> This is a pretty good reason for the newsreader to leave it alone.
>>>>> "RP" == Richard Pieri <ratinox@unilab.dfci.harvard.edu> writes:
RP> Or a pretty good reason to massage it into something that a human can
RP> more easilly parse.
Well, that is what nn tried to do with Re^4: and Lotus try to do with
the "- Reply" string.
I'd say massage the subject as much as you want for presentation
purposes in the article and subject buffers, but when you generate a
reply or followup, make the default subject line be in strict
compliance with The Seal and with Son-of-RFC1036.
next prev parent reply other threads:[~1996-05-14 15:25 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 ` Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch)) Jason L Tibbitts III
1996-05-14 12:25 ` Per Abrahamsen
1996-05-14 14:32 ` Richard Pieri
1996-05-14 15:25 ` Per Abrahamsen [this message]
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=rj7muf9t0s.fsf@babbage.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).