From: Richard Biener <richard.guenther@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Joern Rennecke <gnu@amylaar.uk>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] PATCH for Re: Stepping down as maintainer for ARC and Epiphany
Date: Tue, 21 May 2024 08:05:09 +0200 [thread overview]
Message-ID: <CAFiYyc04g13gwAUP0XHXa=HONcPMNs_RDLSecTEfJoybyFTB6Q@mail.gmail.com> (raw)
In-Reply-To: <c94078cd-64a9-24ee-ed92-d7301991381c@pfeifer.com>
On Mon, May 20, 2024 at 4:45 PM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> On Wed, 5 Jul 2023, Joern Rennecke wrote:
> > I haven't worked with these targets in years and can't really do
> > sensible maintenance or reviews of patches for them. I am currently
> > working on optimizations for other ports like RISC-V.
>
> I noticed MAINTAINERS was not updated, so pushed the patch below.
That leaves the epiphany port unmaintained. Should we automatically add such
ports to the list of obsoleted ports?
Richard.
> Gerald
>
>
> commit f94598ffaf5affbc9421ff230502357b07c55d9c
> Author: Gerald Pfeifer <gerald@pfeifer.com>
> Date: Mon May 20 16:43:05 2024 +0200
>
> MAINTAINERS: Update Joern Rennecke's status
>
> This is per his mail to gcc@gcc.gnu.org on 7 Jul 2023.
>
> ChangeLog:
> * MAINTAINERS: Move Joern Rennecke from arc and epiphany maintainer
> to Write After Approval.
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8e0add6bef8..e2870eef2ef 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -56,7 +56,6 @@ aarch64 port Kyrylo Tkachov <ktkachov@gcc.gnu.org>
> alpha port Richard Henderson <rth@gcc.gnu.org>
> amdgcn port Julian Brown <julian@codesourcery.com>
> amdgcn port Andrew Stubbs <ams@baylibre.com>
> -arc port Joern Rennecke <gnu@amylaar.uk>
> arc port Claudiu Zissulescu <claziss@synopsys.com>
> arm port Nick Clifton <nickc@redhat.com>
> arm port Richard Earnshaw <richard.earnshaw@arm.com>
> @@ -68,7 +67,6 @@ c6x port Bernd Schmidt <bernds_cb1@t-online.de>
> cris port Hans-Peter Nilsson <hp@axis.com>
> c-sky port Xianmiao Qu <cooper.qu@linux.alibaba.com>
> c-sky port Yunhai Shang <yunhai@linux.alibaba.com>
> -epiphany port Joern Rennecke <gnu@amylaar.uk>
> fr30 port Nick Clifton <nickc@redhat.com>
> frv port Nick Clifton <nickc@redhat.com>
> frv port Alexandre Oliva <aoliva@gcc.gnu.org>
> @@ -634,6 +632,7 @@ Joe Ramsay <joe.ramsay@arm.com>
> Rolf Rasmussen <rolfwr@gcc.gnu.org>
> Fritz Reese <fritzoreese@gmail.com>
> Volker Reichelt <v.reichelt@netcologne.de>
> +Joern Rennecke <gnu@amylaar.uk>
> Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
> Tom Rix <trix@redhat.com>
> Thomas Rodgers <trodgers@redhat.com>
next prev parent reply other threads:[~2024-05-21 6:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1688582633587.6.46186@webmail-backend-production-7b8b7bc877-jfhdl>
2023-07-06 6:17 ` Richard Biener
2023-07-07 0:37 ` Jeff Law
2024-05-20 14:44 ` [committed] PATCH for " Gerald Pfeifer
2024-05-21 6:05 ` Richard Biener [this message]
2024-05-21 13:57 ` Jeff Law
2024-05-21 14:02 ` Paul Koning
2024-05-21 16:21 ` Jeff Law
2024-05-21 16:43 ` Richard Biener
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='CAFiYyc04g13gwAUP0XHXa=HONcPMNs_RDLSecTEfJoybyFTB6Q@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=gnu@amylaar.uk \
/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).