From: caiyinyu <caiyinyu@loongson.cn>
To: Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>,
Xi Ruoyao <xry111@xry111.site>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: Appointing an official maintainer for LoongArch.
Date: Thu, 25 Aug 2022 12:04:07 +0800 [thread overview]
Message-ID: <830a7db4-6616-9460-e272-ea00fbd577fd@loongson.cn> (raw)
In-Reply-To: <98f3d78d-32e1-152f-f03f-dca11383cc72@redhat.com>
在 2022/8/23 上午5:22, Carlos O'Donell 写道:
> Community,
>
> I would like to us to appoint a maintainer for LoongArch.
>
> All ports in glibc should have machine maintainers:
> https://sourceware.org/glibc/wiki/MAINTAINERS
>
> The responsibility of the machine maintainer is to test and support
> the target machine in upstream glibc. Generally this includes reviewing
> architecture specific patches from developers and helping test during
> the release freeze.
>
> Given that Caiyin Yu submitted the port I think that they would be
> an excellent choice as maintainer.
>
> Caiyin,
>
> Would you be interested in being the glibc maintainer for the LoongArch
> machine architecture?
>
> I would be more than happy to help you with any questions you have as
> you support the machine port.
>
I'm very happy to be the glibc maintainer for the LoongArch
machine architecture.
I have created an new glibc wiki account
with name Yinyu Cai and email caiyinyu@loongson.cn (the previous
account are gone) and I need to participate in the glibc wiki
to edit loongarch parts.
Thanks.
next prev parent reply other threads:[~2022-08-25 4:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 21:22 Carlos O'Donell
2022-08-25 4:04 ` caiyinyu [this message]
2022-08-31 9:00 ` Ping: " caiyinyu
2022-09-05 10:32 ` caiyinyu
2022-09-05 13:37 ` Adhemerval Zanella Netto
2022-09-29 13:03 ` caiyinyu
2022-10-17 12:10 ` Siddhesh Poyarekar
2022-10-17 13:23 ` Carlos O'Donell
2022-10-17 9:23 ` caiyinyu
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=830a7db4-6616-9460-e272-ea00fbd577fd@loongson.cn \
--to=caiyinyu@loongson.cn \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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).