git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: git@vger.kernel.org, Jason Pyeron <jpyeron@pdinc.us>
Subject: Re: [OT] List CC etiquette and my brain just do not seem to work
Date: Sun, 15 Jun 2014 16:44:36 +0000	[thread overview]
Message-ID: <20140615164436.GF368384@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <3ECA2E24768746D78A799ED85F4856CA@black>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

On Sun, Jun 15, 2014 at 10:27:21AM -0400, Jason Pyeron wrote:
> <rant>
> Why can the list set the reply to the list and if there is a sender
> whos email is not on the list add them to the reply to header as well.

https://www.google.com/search?q=reply+to+considered+harmful

> I forget too many times to fix the address lines, and I get beaten
> with a stick at work when I use the reply all.

I have to adjust to different behavior for different lists as well.  On
the Debian lists, you are expected to reply to the list only, unless
someone sets their Mail-Followup-To accordingly, in which case your mail
client should do the right thing and CC them.

On the Git list, you are expected to CC everybody.  I personally prefer
the Debian strategy, as I read the list and don't generally need the
extra copy, but when in Rome….

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-06-15 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-15 14:27 [OT] List CC etiquette and my brain just do not seem to work Jason Pyeron
2014-06-15 16:44 ` brian m. carlson [this message]
2014-06-15 17:25   ` Jason Pyeron

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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=20140615164436.GF368384@vauxhall.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=jpyeron@pdinc.us \
    /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://80x24.org/mirrors/git.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).