From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>, gcc@gcc.gnu.org
Subject: Re: Separate commit mailing lists for trunk/branches possible?
Date: Sun, 19 Jul 2020 22:56:07 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2007192240070.234068@eddie.linux-mips.org> (raw)
In-Reply-To: <20200719211539.GA108109@elastic.org>
On Sun, 19 Jul 2020, Frank Ch. Eigler wrote:
> > 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.
Maybe it's me tilting at windmills, but waste accumulates. If everyone
ignores a small waste of resources, then eventually they'll run out. And
I'm not sure if it's human attention time or the environment that is most
valuable, and all the resources we use for networking have environmental
impact. Time is already wasted every day on even less important issues,
some of which caused by other people actually not paying enough attention.
FWIW,
Maciej
next prev parent reply other threads:[~2020-07-19 21:56 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
2020-07-19 21:56 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.21.2007192240070.234068@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.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).