From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Frank Scheiner <frank.scheiner@web.de>
Cc: "Peter Bergner" <bergner@linux.ibm.com>,
"Richard Biener" <rguenther@suse.de>,
"René Rebe" <rene@exactcode.de>,
"GCC Administrator via Gcc" <gcc@gcc.gnu.org>,
jeffreyalaw@gmail.com
Subject: Re: Stepping up as maintainer for ia64
Date: Fri, 8 Mar 2024 23:28:08 +0000 [thread overview]
Message-ID: <CAH6eHdRrqrVP=RtV8=bkSKdLtAkJ0TUPCZ5fXRz8jppn3F72Zw@mail.gmail.com> (raw)
In-Reply-To: <67244113-4ebd-4ef7-aad3-dd3593cda532@web.de>
On Fri, 8 Mar 2024 at 22:35, Frank Scheiner via Gcc <gcc@gcc.gnu.org> wrote:
>
> On 08.03.24 23:00, Peter Bergner wrote:
> > On 3/8/24 7:16 AM, Richard Biener via Gcc wrote:
> >> I CCed Jeff who is on the commitee to forward the maintainer proposal
> >> though I guess this will not go forward as a first step. Instead
> >> you are probably expected to show activity on the port, for example
> >> post the patch series to make ia64 use LRA, get write access to the
> >> git repository and then be promoted maintainer.
> >
> > One other method for showing activity is posting regular testsuite
> > results on the gcc-testresults mailing list to show the community
> > the port is "working".
>
> I don't want to spam this or the other list each and every week, but I
Sending test results to the gcc-testresults list is **not** spamming,
that's what the list is for!
https://gcc.gnu.org/pipermail/gcc-testresults/2024-March/date.html
If you're testing uncommon targets (e.g. ia64-linux) then sending test
results to the list is essential so we know the target builds, because
nobody else is testing it.
next prev parent reply other threads:[~2024-03-08 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 17:52 René Rebe
2024-03-07 19:08 ` Richard Biener
2024-03-08 8:54 ` René Rebe
2024-03-08 13:16 ` Richard Biener
2024-03-08 22:00 ` Peter Bergner
2024-03-08 22:31 ` Frank Scheiner
2024-03-08 23:28 ` Jonathan Wakely [this message]
2024-03-09 2:18 ` Peter Bergner
2024-03-09 17:08 ` Frank Scheiner
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='CAH6eHdRrqrVP=RtV8=bkSKdLtAkJ0TUPCZ5fXRz8jppn3F72Zw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=bergner@linux.ibm.com \
--cc=frank.scheiner@web.de \
--cc=gcc@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--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).