From: Jing Yu <jingyu@google.com>
To: overseers@sourceware.org
Cc: Cary Coutant <ccoutant@google.com>
Subject: Need write access to binutils project
Date: Wed, 02 Jul 2014 20:01:00 -0000 [thread overview]
Message-ID: <CAJ_rGWTPiW4S6y62aNGO+SvUSr5Na5ct=btGTjN5WwHiwc2HUQ@mail.gmail.com> (raw)
Hi overseers,
I already have an account for committing gcc patches: jingyu@gcc.gnu.org
Cary Coutant approved my write access to binutils.
Could you please grant me the permission?
Thanks,
Jing
next reply other threads:[~2014-07-02 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 20:01 Jing Yu [this message]
2014-07-03 0:27 ` Ian Lance Taylor
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='CAJ_rGWTPiW4S6y62aNGO+SvUSr5Na5ct=btGTjN5WwHiwc2HUQ@mail.gmail.com' \
--to=jingyu@google.com \
--cc=ccoutant@google.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).