From: Jonathan Wakely <jwakely@redhat.com>
To: Rene Rebe <rene@exactcode.de>
Cc: gcc-patches@gcc.gnu.org, rguenther@suse.de, frank.scheiner@web.de
Subject: Re: [PATCH 3/3] MAINTAINERS: Add myself as IA-64 maintainer.
Date: Wed, 12 Jun 2024 20:03:59 +0100 [thread overview]
Message-ID: <ZmnxH_ka2XR0habe@zen.kayari.org> (raw)
In-Reply-To: <20240612.124314.2208246965805850070.rene@exactcode.de>
On 12/06/24 12:43 +0200, Rene Rebe wrote:
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/MAINTAINERS b/MAINTAINERS
>index e2870eef2ef..4328ca5f84c 100644
>--- a/MAINTAINERS
>+++ b/MAINTAINERS
>@@ -78,6 +78,7 @@ i386 port Jan Hubicka <hubicka@ucw.cz>
> i386 port Uros Bizjak <ubizjak@gmail.com>
> i386 vector ISA extns Kirill Yukhin <kirill.yukhin@gmail.com>
> i386 vector ISA extns Hongtao Liu <hongtao.liu@intel.com>
>+ia64 port René Rebe <rene.rebe@exactcode.com>
I think this change should only happen if/when you're officially
appointed as the port maintainer by the steering committee.
Port maintainers are expected to have a track record of good commits
before being appointed.
Just sending patches to resurrect the port and posting testresults
seems OK for now.
> iq2000 port Nick Clifton <nickc@redhat.com>
> lm32 port Sebastien Bourdeauducq <sebastien@milkymist.org>
> LoongArch port Chenghua Xu <xuchenghua@loongson.cn>
>--
>2.45.0
>
>
>--
> René Rebe, ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
> https://exactcode.com | https://t2sde.org | https://rene.rebe.de
next prev parent reply other threads:[~2024-06-12 19:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45833A6D-A84C-4276-AADB-BE2923886F64@exactcode.de>
[not found] ` <A935D68A-1B29-421A-A239-52CA50ADA239@suse.de>
[not found] ` <3DAB006A-ACE2-4BEC-AA01-87625DBEE259@exactcode.de>
2024-06-12 10:33 ` [PATCH 0/3] Remove ia64*-*-linux from the list of obsolete targets Rene Rebe
2024-06-12 10:42 ` [PATCH 1/3] " Rene Rebe
2024-06-12 18:40 ` Jonathan Wakely
2024-06-12 18:48 ` Jonathan Wakely
2024-06-13 8:58 ` Gerald Pfeifer
2024-06-12 10:42 ` [PATCH 2/3] Enabled LRA for ia64 Rene Rebe
2024-06-12 11:01 ` Richard Biener
2024-06-12 12:50 ` René Rebe
2024-06-12 13:00 ` Richard Biener
2024-06-12 13:19 ` René Rebe
2024-06-12 14:03 ` Frank Scheiner
2024-06-12 14:09 ` Frank Scheiner
2024-06-12 18:54 ` Jonathan Wakely
2024-06-12 20:59 ` Frank Scheiner
2024-06-13 10:33 ` Jonathan Wakely
2024-06-13 14:11 ` Jeff Law
2024-06-13 14:16 ` Jonathan Wakely
2024-06-13 14:18 ` Jonathan Wakely
2024-06-14 11:07 ` Frank Scheiner
2024-06-14 12:53 ` Jonathan Wakely
2024-06-14 13:07 ` Frank Scheiner
2024-06-14 13:23 ` Jonathan Wakely
2024-06-17 18:03 ` Joseph Myers
2024-06-17 18:53 ` Jonathan Wakely
2024-06-17 19:36 ` Frank Scheiner
2024-06-13 7:02 ` Richard Biener
2024-06-12 10:43 ` [PATCH 3/3] MAINTAINERS: Add myself as IA-64 maintainer Rene Rebe
2024-06-12 19:03 ` Jonathan Wakely [this message]
2024-06-12 18:44 ` [PATCH 0/3] Remove ia64*-*-linux from the list of obsolete targets Jonathan Wakely
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=ZmnxH_ka2XR0habe@zen.kayari.org \
--to=jwakely@redhat.com \
--cc=frank.scheiner@web.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=rene@exactcode.de \
--cc=rguenther@suse.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).