From: "Bin Bin NL Lv" <shlb@cn.ibm.com>
To: overseers@gcc.gnu.org
Cc: mrmeissn@us.ibm.com
Subject: Add access to the GCC repository
Date: Tue, 05 Nov 2019 02:19:00 -0000 [thread overview]
Message-ID: <OFDC0AA482.154DBAA3-ON482584A9.000BDEF2-482584A9.000CA48E@notes.na.collabserv.com> (raw)
Hi dear,
May I have the access for the GCC repository, thanks very much.
Account: shlb@sourceware.org
Sponsor: Michael R Meissner (mrmeissn@us.ibm.com)
Best Regards,
Binbin Lv (吕彬彬)
IBM China Systems & Technology Lab (CSTL)
Address: Building A1, 55 Chuanhe Road, Zhangjiang, Pudong New District,
Shanghai 201210, China
Email: shlb@cn.ibm.com
Mobile Phone: (86)18818203413
next reply other threads:[~2019-11-05 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 2:19 Bin Bin NL Lv [this message]
2019-11-05 2:32 ` Christopher Faylor
2020-03-11 6:11 ` Bin Bin NL Lv
2020-03-11 13:24 ` Frank Ch. Eigler
2020-03-12 4:53 ` Bin Bin NL Lv
2020-03-11 7:00 ` Bin Bin NL Lv
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=OFDC0AA482.154DBAA3-ON482584A9.000BDEF2-482584A9.000CA48E@notes.na.collabserv.com \
--to=shlb@cn.ibm.com \
--cc=mrmeissn@us.ibm.com \
--cc=overseers@gcc.gnu.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).