From: Tobias Burnus <burnus@net-b.de>
To: Thomas Koenig <tkoenig@netcologne.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: [patch, doc] Update people who can review gfortran patches
Date: Fri, 25 Sep 2020 09:34:36 +0200 [thread overview]
Message-ID: <1a57b83d-6060-994f-9709-14b3ca6d5468@net-b.de> (raw)
In-Reply-To: <2b079e88-6065-8d81-2e7d-27b3cbf6652b@netcologne.de>
On 9/25/20 8:02 AM, Thomas Koenig via Fortran wrote:
> for review of its patches, gfortran relies on a group of people
> who can approve patches. Unfortuntately, many of them are not
> active. Others, who have the capability and who have acted as
> de facto approvers (without anybody minding) are missing.
I think you want to link to
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=MAINTAINERS
which is the official list. — At least additionally.
I note the the HTML page states "contributions will be reviewed"
and not "approved" – and (nearly) any review comment is welcome,
be it from an experienced maintainer or just by someone who passes
by. Still, it is a bit misleading if this list includes
someone who is not an official reviewer.
New reviewers get added by approval of the steering committee
(https://gcc.gnu.org/steering.html, typically by some existing
maintainer/reviewer proposing a new one – by sending a private
email to one of the SC members.)
Regarding Jakub: while he is a global reviewer and very active,
for Fortran, he is mostly reviewing OpenMP and – to a lesser extent –
OpenACC patches and only a very few other patches. Thus, listing
him under 'contributions will be reviewed' is a bit misleading.
Cheers,
Tobias
prev parent reply other threads:[~2020-09-25 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 6:02 Thomas Koenig
2020-09-25 6:54 ` Toon Moene
2020-09-25 7:34 ` Tobias Burnus [this message]
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=1a57b83d-6060-994f-9709-14b3ca6d5468@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).