From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: overseers@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: Separate commit mailing lists for trunk/branches possible?
Date: Fri, 17 Jul 2020 19:05:48 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2007171838300.234068@eddie.linux-mips.org> (raw)
Hi,
As you have probably been well-aware the amount of traffic sent to the
<gcc-cvs@gcc.gnu.org> mailing list has grown dramatically since the switch
to GIT. Last month alone I received over 13000 messages, which accounted
for ~18.5% of all my incoming traffic. And right now another mailbomb has
been in progress; since midnight I have received over 3700 messages so
far.
Most of this stuff is vendor branch stuff I find completely uninteresting
to me and which from my point of view is a waste of resources. I could
filter it to /dev/null via `procmail', but that would still be a waste.
Would it be reasonable to have the mailing list split into more than one,
that is at least the original covering the trunk, and then one or more for
branches?
Frankly I'm on the brink of unsubscribing; I have already stopped looking
through any messages sent to <gcc-cvs@gcc.gnu.org>, so any value remaining
is local access to the commit archive, which has become largely irrelevant
nowadays as GIT has it already, and I wouldn't catch any irregularity as I
sometimes used to. But I can't stand the traffic really anymore.
Thoughts?
Maciej
next reply other threads:[~2020-07-17 18:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 18:05 Maciej W. Rozycki [this message]
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
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.2007171838300.234068@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.gnu.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).