From: Chris Torek <chris.torek@gmail.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] documentation: send-email: use camel case consistently
Date: Tue, 20 Feb 2024 16:43:26 -0800 [thread overview]
Message-ID: <CAPx1GvcGhZLqHVz9=ZW-w+ebP64-8FpPSb_ef7ygXzDDTze2bA@mail.gmail.com> (raw)
In-Reply-To: <9d0022ba5666223af94bbf450909b1ba@manjaro.org>
On Tue, Feb 20, 2024 at 8:42 AM Dragan Simic <dsimic@manjaro.org> wrote:
> I've never ever seen anyone referring to email headers as "TO", "CC" or
> "BCC". It's always referred to as "To", "Cc" and "Bcc".
I used some email system (back in the early 1980s) that did that. It
felt weird even then. I can't remember if it was some CSMail (CSNet)
or MH(Rand Mail Handler) version that did it.
> Thus, "cc" stems from the old age of literal carbon copies ...
That's correct. However:
> and "bcc" was seemingly coined when email took over.
"Blind Carbon Copies" predated email, but required adding the
notation separately, if it was to be added at all. (I'm just old enough
to remember using carbon copies myself, but not old enough to
know what Standard Office Practice was at that time.)
Whether adding a "bcc" notation was common I don't know;
it seems it would be easier to leave it off if you made, say, one
original and a total of 2 copies, one "blinded".
(As your Wikipedia link notes, there was a practical limit to how
many carbon copies one could make in the first place.)
Chris
next prev parent reply other threads:[~2024-02-21 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 5:19 [PATCH] documentation: send-email: use camel case consistently Dragan Simic
2024-02-20 0:52 ` Junio C Hamano
2024-02-20 6:41 ` Dragan Simic
2024-02-20 16:22 ` Junio C Hamano
2024-02-20 16:29 ` Dragan Simic
2024-02-20 16:50 ` Dragan Simic
2024-02-20 18:29 ` Junio C Hamano
2024-02-20 19:38 ` Dragan Simic
2024-02-21 0:43 ` Chris Torek [this message]
2024-02-21 7:50 ` Dragan Simic
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='CAPx1GvcGhZLqHVz9=ZW-w+ebP64-8FpPSb_ef7ygXzDDTze2bA@mail.gmail.com' \
--to=chris.torek@gmail.com \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).