unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-26 0d8bae5: Fix capitalization of mail headers
Date: Sun, 20 May 2018 16:33:53 +0200	[thread overview]
Message-ID: <87fu2ms8fi.fsf@igel.home> (raw)
In-Reply-To: <jwv1se630ld.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Sun, 20 May 2018 09:47:45 -0400")

On Mai 20 2018, Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:

>> -The @samp{To}, @samp{Cc}, and @samp{Bcc} fields can appear any number
>> +The @samp{To}, @samp{CC}, and @samp{BCC} fields can appear any number
>
> FWIW, I can't remember seeing "CC:" or "BCC:" in an email message
> whereas I've seen "Cc:" and "Bcc:" many many times.  So my reaction to
> the above line would be "Huh?  Why didn't they write `TO` to
> be consistent?"

Also, RFC 2822 always uses the capitalized form (the only exception is
Message-ID).

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."



  reply	other threads:[~2018-05-20 14:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180520090853.27430.88055@vcs0.savannah.gnu.org>
     [not found] ` <20180520090853.BA0E920468@vcs0.savannah.gnu.org>
2018-05-20 13:47   ` [Emacs-diffs] emacs-26 0d8bae5: Fix capitalization of mail headers Stefan Monnier
2018-05-20 14:33     ` Andreas Schwab [this message]
2018-05-20 22:29       ` Stefan Monnier
2018-05-21  4:15       ` Richard Stallman
2018-05-21 15:13         ` Eli Zaretskii
2018-05-20 15:48     ` Eli Zaretskii
2018-05-20 18:08       ` Paul Eggert
2018-05-20 18:33         ` Eli Zaretskii
2018-05-21  0:24           ` Paul Eggert
2018-05-21  2:39             ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fu2ms8fi.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).