public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: caiyinyu <caiyinyu@loongson.cn>
To: libc-alpha <libc-alpha@sourceware.org>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: Re: Ping: Appointing an official maintainer for LoongArch.
Date: Mon, 5 Sep 2022 18:32:23 +0800	[thread overview]
Message-ID: <cf222a28-0481-acdc-d9b6-abcb0dab2532@loongson.cn> (raw)
In-Reply-To: <4efd9ab1-3812-a1c9-f163-915d2a763c37@loongson.cn>


在 2022/8/31 下午5:00, caiyinyu 写道:
> Gentle ping.
>
> 在 2022/8/25 下午12:04, caiyinyu 写道:
>>
>> 在 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.
>>
>>
Hi,

I am still not in the glibc wiki EditGroup.

I tried to upload files (More Actions -> Load) to update 
LoongArch-related info

but failed and I need permission to do these things.

I'm new here, so if there are any mistakes, please let me know.

Thanks.


>>
>>


  reply	other threads:[~2022-09-05 10:32 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
2022-08-31  9:00   ` Ping: " caiyinyu
2022-09-05 10:32     ` caiyinyu [this message]
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=cf222a28-0481-acdc-d9b6-abcb0dab2532@loongson.cn \
    --to=caiyinyu@loongson.cn \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /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).