From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Feng Xue <fxue@os.amperecomputing.com>
Cc: "overseers@sourceware.org" <overseers@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: Request for commit access to glibc
Date: Fri, 18 Jan 2019 04:05:00 -0000 [thread overview]
Message-ID: <20190118040549.GA14528@ednor.casa.cgf.cx> (raw)
In-Reply-To: <BL0PR01MB4593D8CB185CA412AD07F14EF79C0@BL0PR01MB4593.prod.exchangelabs.com>
On Fri, Jan 18, 2019 at 01:36:58AM +0000, Feng Xue wrote:
>Overseers,
>
>Please add me (fxue@sourceware.org) to the glibc group after verifying
>with Carlos O'Donell.
>
>Carlos O'Donell vouches for my sanity and competence.
>
>I truly understand FSF copyright protocols, and always respect
>per-branch policies on what I am allowed to touch and how.
You already have an account with glibc access. You filled out a form on
1/16 requesting an account with glibc access. That account was created
on 1/16 at 16:35 UTC.
next prev parent reply other threads:[~2019-01-18 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 1:37 Feng Xue
2019-01-18 4:05 ` Christopher Faylor [this message]
2019-01-18 9:17 ` Feng Xue
2019-01-18 18:51 ` Carlos O'Donell
2019-01-19 6:58 ` Christopher Faylor
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=20190118040549.GA14528@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=carlos@redhat.com \
--cc=fxue@os.amperecomputing.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).