From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: coff@tuhs.org, tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] [COFF] Book Recommendation
Date: Mon, 6 Dec 2021 09:29:24 -0500 (EST) [thread overview]
Message-ID: <20211206142924.A8A7118C079@mercury.lcs.mit.edu> (raw)
OK, this is my last _civil_ request to stop email-bombing both lists with
trafic. In the future, I will say publicly _exactly_ what I think - and if
screens still had phosphor, it would probably peel it off.
I can see that there are cases when one might validly want to post to both
lists - e.g. when starting a new discusson. However, one of the two should
_always_ be BCC'd, so that simple use of reply won't generate a copy to
both. I would suggest that one might say something like 'this discussion is
probably best continued on the <foo> list' - which could be seeded by BCCing
the _other_.
Thank you.
Noel
next reply other threads:[~2021-12-06 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 14:29 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 2:50 [TUHS] " Douglas McIlroy
2021-12-06 4:25 ` Adam Thornton
2021-12-06 14:11 ` [TUHS] [COFF] " Clem Cole
2021-12-06 14:22 ` Dan Cross
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=20211206142924.A8A7118C079@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=coff@tuhs.org \
--cc=tuhs@tuhs.org \
/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).