Computer Old Farts Forum
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: coff@tuhs.org, tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [COFF] [TUHS] 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
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

             reply	other threads:[~2021-12-06 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 14:29 Noel Chiappa [this message]
     [not found] <CAKH6PiWtxq7vwh_WdVtZx9-qqN5aNr+t14eTAJx9-eLWjYF0BQ@mail.gmail.com>
2021-12-06  4:25 ` Adam Thornton
2021-12-06 14:11   ` Clem Cole
2021-12-06 14:22     ` Dan Cross
     [not found] <CAKH6PiU59OwWNC3so20muvECi+2HKaX2PRAizjLjjO1J=Vwgug@mail.gmail.com>
     [not found] ` <20211116040858.se3ygq2butxqopcx@localhost.localdomain>
     [not found]   ` <CAC20D2Phn_VahO7A2MCEHgMRV7isVo9W3s6wqdvw6Q=0koE9jg@mail.gmail.com>
     [not found]     ` <CAFH29tq3J2=dUEufiUApMgWBAFogYfj-nWL5C2WD950xW59_4A@mail.gmail.com>
     [not found]       ` <CAP2nic0d7Kg1-i3w=6220NfBTQh7TaZ6nMsNx7NWLE+dTn5Z7w@mail.gmail.com>
2021-11-16 16:19         ` Clem Cole
     [not found] <CAKH6PiXtVetBZbyvOiWZFSTvNebSTEuaYkOoUx4KPg4wtdvN8g@mail.gmail.com>
     [not found] ` <CAFH29tomxKDFn-pRBT21-X+m4ugzzn-tuGyY-Cq0hN6i5-=oeQ@mail.gmail.com>
2021-11-16 15:53   ` Adam Thornton
     [not found] ` <b355e6b8-720d-3078-d54a-2beb5ff79bd4@mhorton.net>
     [not found]   ` <CAEdTPBdVnPQMaDX0jOL81EkL1M7Eg=U4qWPwKMsr6SBc2Zz9vw@mail.gmail.com>
2021-11-23 15:23     ` Clem Cole
2021-11-23 19:40     ` 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).