From: Simon Josefsson <jas@extundo.com>
Subject: Re: " (was: " hardcoded in message-change-subject (patch)
Date: Wed, 29 Jan 2003 18:58:12 +0100 [thread overview]
Message-ID: <ilur8avn8i3.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87el6vkhlz.fsf@unix.home> (deskpot@myrealbox.com's message of "Wed, 29 Jan 2003 20:09:44 +0300")
deskpot@myrealbox.com (Vasily Korytov) writes:
> I've noted, ``was:'', inserted by message-change-subject, is lowercase.
> I think, it would be nicer to have it capitalized (as ``Re:''), but I'm
> not sure, everyone would agree with it (opinions, anyone?).
FWIW, the usefor draft uses lower case "was:":
,----
| In the following examples, please note that only "Re: " is mandated
| by this standard. "was: " is a convention used by many English-
| speaking posters to signal a change in subject matter. Software can
| always recognize such changes from the References-header.
|
| Subject: Film at 11
| Subject: Re: Film at 11
| Subject: Godwin's law considered harmful (was: Film at 11)
| Subject: Godwin's law (was: Film at 11)
| Subject: Re: Godwin's law (was: Film at 11)
| Subject: Re: Godwin's law
`----
I could not find a more canonical specification of it.
> Attached is the patch for making "was: " go in a variable to make
> everyone happy.
If it is added, IMHO it should not be advertised much or include a
prominent warning in the docstring that changing it from the default
can cause irritation. Compare the bad behaviour caused by some MUAs
that translate Re: etc.
next prev parent reply other threads:[~2003-01-29 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 17:09 Vasily Korytov
2003-01-29 17:58 ` Simon Josefsson [this message]
2003-01-29 18:08 ` Vasily Korytov
2003-02-01 16:29 ` " 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=ilur8avn8i3.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).