From: liuzhensong <liuzhensong@loongson.cn>
To: overseers@sourceware.org
Subject: Apply to a new LoongArch port maintainer
Date: Mon, 29 Nov 2021 17:13:55 +0800 [thread overview]
Message-ID: <8a7f8ab8-fba1-801c-a9b3-455d41bb2b82@loongson.cn> (raw)
In-Reply-To: <401c72f5-49df-1660-1878-b062ea71ef0f@loongson.cn>
> -----原始邮件-----
> 发件人: "Alan Modra" <amodra@gmail.com>
> 发送时间: 2021-10-28 20:39:02 (星期四)
> 收件人: "Chenghua Xu" <xuchenghua@loongson.cn>
> 抄送: binutils@sourceware.org, paul.hua.gm@gmail.com,
liuzhensong@loongson.cn
> 主题: Re: [PATCH LoongArch v3 0/5] Add LoongArch support.
>
> On Tue, Oct 26, 2021 at 06:01:58PM +0800, Chenghua Xu wrote:
> > We apply for Zhensong Liu and me to be the maintainers of the LoongArch
> > port.
>
> Thank you. Please email overseers@sourcware.org requesting write
> access to the binutils-gdb repository nominating me as sponsor. Your
> first commit can be to binutils/MAINTAINERS adding your names and
> email as maintainers for LoongArch. Also, create accounts on
> https://sourceware.org/bugzilla if you haven't done so already,
> preferably with the same email address.
>
> --
> Alan Modra
> Australia Development Lab, IBM
hi
I'm very happy to be a maintainer of LoongArch, please add write access
for the binutils-gdb repository.
I applied for an account at
https://sourceware.org/bugzilla/createaccount.cgi but failed, then what
should I do?
next parent reply other threads:[~2021-11-29 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <401c72f5-49df-1660-1878-b062ea71ef0f@loongson.cn>
2021-11-29 9:13 ` liuzhensong [this message]
2021-12-01 19:35 ` Christopher Faylor
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=8a7f8ab8-fba1-801c-a9b3-455d41bb2b82@loongson.cn \
--to=liuzhensong@loongson.cn \
--cc=overseers@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).