From: Ian Lance Taylor <ian@airs.com>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: overseers@sourceware.org, carlos@redhat.com,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: Glibc write access
Date: Tue, 06 Jan 2015 13:37:00 -0000 [thread overview]
Message-ID: <m3oaqct4h5.fsf@pepe.airs.com> (raw)
In-Reply-To: <54ABCA86.5040403@arm.com> (Richard Earnshaw's message of "Tue, 06 Jan 2015 11:44:06 +0000")
Richard Earnshaw <rearnsha@arm.com> writes:
> Please can I have write access to the glibc tree? My existing
> sourceware account name is rearnsha.
>
> Carlos/Marcus should be able to approve.
Done.
Ian
next prev parent reply other threads:[~2015-01-06 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 11:44 Richard Earnshaw
2015-01-06 11:58 ` Marcus Shawcroft
2015-01-06 13:37 ` Ian Lance Taylor [this message]
2015-01-06 14:16 ` Carlos O'Donell
2019-02-20 14:09 Martin Liška
2019-02-20 14:28 ` Martin Liška
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=m3oaqct4h5.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=carlos@redhat.com \
--cc=overseers@sourceware.org \
--cc=rearnsha@arm.com \
/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).