From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org
Cc: cuilili8868@gmail.com, crazylht@gmail.com
Subject: Re: Request from Lili Cui
Date: Wed, 15 Jun 2022 11:13:06 -0400 [thread overview]
Message-ID: <20220615151306.xkog536smhrwvmxp@cgf.cx> (raw)
In-Reply-To: <20220615013635.2FCB0385703E@sourceware.org>
On Wed, Jun 15, 2022 at 01:36:35AM +0000, cuilili8868--- via Overseers wrote:
>Lili Cui is requesting an account:
>
>Login: lilicui
>Email: cuilili8868@gmail.com
>Project: gcc
>Approver: crazylht@gmail.com
This person is not a gcc maintainer so, nope, no account for you.
next prev parent reply other threads:[~2022-06-15 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 1:36 cuilili8868
2022-06-15 15:13 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-27 7:39 cuilili8868
2022-06-27 13:13 ` Mark Wielaard
2022-06-27 13:24 ` Cui, Lili
2022-06-27 15:06 ` Mark Wielaard
2022-06-28 0:12 ` Cui, Lili
2020-04-02 8:21 lili.cui
2020-04-02 14:19 ` Lu, Hongjiu
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=20220615151306.xkog536smhrwvmxp@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=crazylht@gmail.com \
--cc=cuilili8868@gmail.com \
--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).