From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Stafford Horne <shorne@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: state of the ports
Date: Sun, 04 Feb 2024 12:40:10 +0100 [thread overview]
Message-ID: <6070242.lOV4Wx5bFT@noumea> (raw)
In-Reply-To: <Zb8-r6o73vj2fSJ4@antec>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
>
> Hello,
>
> I it unfortunate that openrisc ended up in NOBODY TRIED, I usually try to test
> the port for each release. However, this time the testing mail slipped through
> my mail filters.
>
> Note, during "glibc 2.36 - Machine testing." Carlos CCed each maintainer on the
> announcement mail. This makes it easier for us maintainers to know we need to
> take action.
>
> Can maintainers be CCed on these announcements going forward?
>
> For 2.39, I see the main only went to the list.
Sorry about that, I promise to do better next time.
Best
-Andreas
>
> -Stafford
>
>
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-04 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 2:35 Andreas K. Huettel
2024-02-02 7:51 ` Xi Ruoyao
2024-02-02 7:53 ` Xi Ruoyao
2024-02-02 11:28 ` Florian Weimer
2024-02-02 21:40 ` Andreas K. Huettel
2024-02-22 17:11 ` Xi Ruoyao
2024-02-22 20:30 ` Andreas K. Huettel
2024-02-04 7:37 ` Stafford Horne
2024-02-04 11:40 ` Andreas K. Huettel [this message]
2024-02-25 22:47 ` Mark Wielaard
2024-02-26 12:44 ` Adhemerval Zanella Netto
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=6070242.lOV4Wx5bFT@noumea \
--to=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.org \
--cc=shorne@gmail.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).