public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Christophe Lyon <christophe.lyon@arm.com>
Cc: binutils@sourceware.org, GCC Mailing List <gcc@gcc.gnu.org>,
	 gdb@sourceware.org, Nick Clifton <nickc@redhat.com>,
	Richard Biener <rguenther@suse.de>,
	Jakub Jelinek <jakub@redhat.com>,
	Joel Brobecker <brobecker@adacore.com>,
	Carlos O'Donell <carlos@redhat.com>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	Thiago Bauermann <thiago.bauermann@linaro.org>,
	 Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Christophe Lyon <christophe.lyon@linaro.org>
Subject: Re: Patches submission policy change
Date: Sat, 06 Apr 2024 18:29:19 +0200	[thread overview]
Message-ID: <d3ab5cdf5aa9bd6edc244aa5fe7ecf8b603da243.camel@klomp.org> (raw)
In-Reply-To: <cda2caa7-99b8-420e-aca4-e06256b9b637@arm.com>

Hi,

On Fri, 2024-04-05 at 09:17 +0200, Christophe Lyon wrote:
> On 4/4/24 23:35, Mark Wielaard wrote:
> > wrt to the mailinglists maybe getting larger patches, I think most
> > will still be under 400K and I wouldn't raise the limit (because most
> > such larger emails are really just spam). But we might want to get
> > more mailinglist moderators.
> > 
> > gcc-patches, binutils and gdb-patches all have only one moderator
> > (Jeff, Ian and Thiago). It would probably be good if there were
> > more.
> > 
> > Any volunteers? It shouldn't be more than 1 to 3 emails a week
> > (sadly most of them spam).
> > 
> I'm happy to help with moderation of any/all of these 3 lists.

I added Simon for gdb, Marc for gcc and you as admin for binutils.
So all three projects now have at least two moderators. Thanks so much
for volunteering.

And please reach out to overseers if this becomes too much of a burden
(it really should not be more than a handful of messages each week).
Then we'll see if we can adjust the (spam) settings so only oversized
messages reach the moderation queues (or raise the limits if that makes
more sense).

Thanks,

Mark

  reply	other threads:[~2024-04-06 16:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  8:22 Christophe Lyon
2024-04-03  8:30 ` Jan Beulich
2024-04-03 13:11   ` Christophe Lyon
2024-04-04  8:12     ` Jan Beulich
2024-04-05  7:22       ` Christophe Lyon
2024-04-03  8:45 ` Jakub Jelinek
2024-04-03  8:49   ` Jan Beulich
2024-04-03  8:57     ` Richard Biener
2024-04-03 10:21       ` Jan Beulich
2024-04-03 12:58         ` Joel Sherrill
2024-04-03 13:23           ` Christophe Lyon
2024-04-08 15:37             ` Richard Earnshaw (lists)
2024-04-03 12:59         ` Jason Merrill
2024-04-03 13:19         ` Christophe Lyon
2024-04-03  9:50   ` Jonathan Wakely
2024-04-03 15:03 ` Simon Marchi
2024-04-04 21:35 ` Mark Wielaard
2024-04-04 21:51   ` Simon Marchi
2024-04-05  6:44   ` Marc
2024-04-05  7:17   ` Christophe Lyon
2024-04-06 16:29     ` Mark Wielaard [this message]
2024-04-07 12:32   ` Jonathan Wakely
2024-04-07 14:02     ` Mark Wielaard
2024-04-07 14:20       ` Jonathan Wakely
2024-04-07 22:00         ` Mark Wielaard

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=d3ab5cdf5aa9bd6edc244aa5fe7ecf8b603da243.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=carlos@redhat.com \
    --cc=christophe.lyon@arm.com \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=nickc@redhat.com \
    --cc=rguenther@suse.de \
    --cc=thiago.bauermann@linaro.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).