From: Paul Clarke <pc@us.ibm.com>
To: overseers@sourceware.org
Cc: "Carlos O'Donell" <carlos@redhat.com>
Subject: Request for glibc commit authority
Date: Tue, 19 Feb 2019 17:58:00 -0000 [thread overview]
Message-ID: <74a31fe4-2993-064f-7edf-f9099e48814c@us.ibm.com> (raw)
Overseers,
Please add me (pc) to the glibc group after verifying with Carlos O'Donell.
Carlos 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.
Thank you,
Paul Clarke
next reply other threads:[~2019-02-19 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 17:58 Paul Clarke [this message]
2019-02-19 18:05 ` Christopher Faylor
2019-02-20 7:23 ` Carlos O'Donell
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=74a31fe4-2993-064f-7edf-f9099e48814c@us.ibm.com \
--to=pc@us.ibm.com \
--cc=carlos@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).