From: Warren Toomey <firstname.lastname@example.org> To: Noel Chiappa <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [TUHS] [COFF] Double posting Date: Tue, 16 Nov 2021 06:57:11 +1000 [thread overview] Message-ID: <20211115205711.GA16126@minnie.tuhs.org> (raw) In-Reply-To: <20211115192726.6AD6818C090@mercury.lcs.mit.edu> On Mon, Nov 15, 2021 at 02:27:26PM -0500, Noel Chiappa wrote: > OK, I can see sending an _initial_ query to both lists, to get it to as wide > a circle as possible: _but_ BCC at least one of them, to prevent lazy people > just hitting 'reply all' and thereby sanding out multiple copies of their > reply. I've just disabled "require explicit destination" on both the TUHS and COFF lists. Let's see if that allows bcc between them. Cheers, Warren
prev parent reply other threads:[~2021-11-15 20:57 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-15 19:27 [TUHS] " Noel Chiappa 2021-11-15 19:57 ` Will Senn 2021-11-15 20:57 ` Warren Toomey [this message]
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=20211115205711.GA16126@minnie.tuhs.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [TUHS] [COFF] Double posting' \ /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
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).