From: Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Separate commit mailing lists for trunk/branches possible?
Date: Fri, 17 Jul 2020 15:48:16 -0400 [thread overview]
Message-ID: <20200717194816.GA13274@cgf.cx> (raw)
In-Reply-To: <alpine.LFD.2.21.2007171838300.234068@eddie.linux-mips.org>
On Fri, Jul 17, 2020 at 07:05:48PM +0100, Maciej W. Rozycki wrote:
> 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.
Actually, it seems like a procmail rule would solve your problem.
next prev parent reply other threads:[~2020-07-17 19:48 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 [this message]
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=20200717194816.GA13274@cgf.cx \
--to=cgf-use-the-mailinglist-please@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=overseers@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).