From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>, gcc@gcc.gnu.org
Subject: Re: Separate commit mailing lists for trunk/branches possible?
Date: Sun, 19 Jul 2020 17:15:39 -0400 [thread overview]
Message-ID: <20200719211539.GA108109@elastic.org> (raw)
In-Reply-To: <alpine.LFD.2.21.2007192152360.234068@eddie.linux-mips.org>
Hi -
> Not the issue of wasted resources including the list server processing
> and sending the messages intended to my address, bandwidth and all the
> network equipment involved on the way, and finally the local mail server
> receiving and dispatching the message to `procmail'. It all does not come
> for free.
FWIW, I'd estimate the incremental infrastructure cost of sending
these messages, over not sending these messages, at pretty close to
zero. The most valuable part is human attention time, which could
make it worthwhile to reduce spamminess.
- FChE
next prev parent reply other threads:[~2020-07-19 21:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 18:05 Maciej W. Rozycki
2020-07-17 18:11 ` Frank Ch. Eigler
2020-07-17 18:46 ` Carlos O'Donell
2020-07-17 19:41 ` Florian Weimer
2020-07-17 20:47 ` Carlos O'Donell
2020-07-17 20:50 ` Joseph Myers
2020-07-17 20:55 ` Frank Ch. Eigler
2020-07-17 19:48 ` Christopher Faylor
2020-07-19 20:57 ` Maciej W. Rozycki
2020-07-19 21:15 ` Frank Ch. Eigler [this message]
2020-07-19 21:56 ` Maciej W. Rozycki
2020-07-17 20:37 ` Joseph Myers
2021-09-27 14:48 overseers&gcc gnu org
2021-10-08 10:49 Maciej W. Rozycki
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=20200719211539.GA108109@elastic.org \
--to=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=macro@linux-mips.org \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).