From: Richard Earnshaw <rearnsha@arm.com>
To: Yufeng Zhang <Yufeng.Zhang@arm.com>
Cc: "overseers@sourceware.org" <overseers@sourceware.org>,
"nickc@redhat.com" <nickc@redhat.com>
Subject: Re: Request for "binutils" cvs write access
Date: Tue, 18 Sep 2012 15:37:00 -0000 [thread overview]
Message-ID: <5058950D.2090003@arm.com> (raw)
In-Reply-To: <50582FEA.9080508@arm.com>
On 18/09/12 09:25, Yufeng Zhang wrote:
> Hi,
>
> I'd like to request for the write after approval access to the binutils
> cvs repo. I have been actively working on the AArch64 binutils port, so
> it will be a lot more convenient if I have the write access to it. Many
> thanks!
>
>
> Kind regards,
> Yufeng Zhang
>
> (Nick and Richard, sorry for bombarding your mailbox with numerous
> request emails; this will be the last one and the one with no error)
>
Nick, I think this would be a good step, but I think it's your call.
R.
next prev parent reply other threads:[~2012-09-18 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 8:25 Yufeng Zhang
2012-09-18 15:37 ` Richard Earnshaw [this message]
2012-09-18 15:38 ` Jeff Law
2012-09-18 23:53 ` 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=5058950D.2090003@arm.com \
--to=rearnsha@arm.com \
--cc=Yufeng.Zhang@arm.com \
--cc=nickc@redhat.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).