From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: YunQiang Su <yunqiang.su@cipunited.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Taking Over MIPS Maintenance
Date: Fri, 19 May 2023 12:20:46 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2305190415170.50034@angie.orcam.me.uk> (raw)
In-Reply-To: <mptlehmytb3.fsf@arm.com>
On Thu, 18 May 2023, Richard Sandiford via Gcc wrote:
> It would be more usual to wait a bit longer until someone becomes
> maintainer. But IMO that's only sensible when there's an existing
> maintainer to cover the interim.
Not questioning YunQiang's overall coding skills I'd be concerned about
following the GNU Coding Standards though, as based on his submissions so
far I'm not convinced of his experience in this area. I would expect a
maintainer to meet the highest standards here.
I have a feeling our overall quality verification has become sloppier
recently and I do wish all the maintainers were as meticulous as you were
when reviewing my MIPS patches years if not decades ago. I do hope it
wasn't just because you considered me so good as to be able to adhere to
the high standards while for other people we just have to accept what we
have been offered.
NB I'll do the MIPS16e2 feature review myself, exceptionally, as I was a
member of the team developing this ISA extension and also did the binutils
part, so I feel somewhat responsible for it and want GCC support for it to
meet the usual quality standard GNU software has built its reputation on.
Maciej
prev parent reply other threads:[~2023-05-19 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 2:49 YunQiang Su
2023-05-18 7:47 ` Richard Sandiford
2023-05-19 11:20 ` Maciej W. Rozycki [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=alpine.DEB.2.21.2305190415170.50034@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=gcc@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
--cc=yunqiang.su@cipunited.com \
/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).