From: Marc <dkm@kataplop.net>
To: Mark Wielaard <mark@klomp.org>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
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>
Subject: Re: Patches submission policy change
Date: Fri, 05 Apr 2024 08:44:28 +0200 [thread overview]
Message-ID: <87sf00xq9f.fsf@arrakis.kataplop.net> (raw)
In-Reply-To: <20240404213501.GL19937@gnu.wildebeest.org> (Mark Wielaard's message of "Thu, 4 Apr 2024 23:35:01 +0200")
Mark Wielaard <mark@klomp.org> writes:
Hello Mark!
> 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).
If still needed, I volunteer for the gcc list!
Marc
next prev parent reply other threads:[~2024-04-05 6:44 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 [this message]
2024-04-05 7:17 ` Christophe Lyon
2024-04-06 16:29 ` Mark Wielaard
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=87sf00xq9f.fsf@arrakis.kataplop.net \
--to=dkm@kataplop.net \
--cc=adhemerval.zanella@linaro.org \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=carlos@redhat.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jakub@redhat.com \
--cc=mark@klomp.org \
--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).