git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] documentation: send-email: use camel case consistently

From
Chris Torek <chris.torek@gmail.com>
Date
Feb 21, 2024, 00:43 UTC
Message-ID
<CAPx1GvcGhZLqHVz9=ZW-w+ebP64-8FpPSb_ef7ygXzDDTze2bA@mail.gmail.com>
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
Previous: Dragan SimicNext: Dragan Simic
Message 9 of 10 in “documentation: send-email: use camel case consistently”
  1. documentation: send-email: use camel case consistentlyDragan Simic, Feb 16, 2024
  2. Junio C HamanoFeb 20, 2024
  3. Dragan SimicFeb 20, 2024
  4. Junio C HamanoFeb 20, 2024
  5. Dragan SimicFeb 20, 2024
  6. Dragan SimicFeb 20, 2024
  7. Junio C HamanoFeb 20, 2024
  8. Dragan SimicFeb 20, 2024
  9. Chris TorekFeb 21, 2024
  10. Dragan SimicFeb 21, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.