From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: <overseers@sourceware.org>
Cc: Roland McGrath <roland@hack.frob.com>
Subject: GLIBC commit access
Date: Mon, 02 Jul 2012 18:46:00 -0000 [thread overview]
Message-ID: <6AF787AB-0944-48F4-8DE1-B86FE092A81E@codesourcery.com> (raw)
Overseers,
Would you please add my sourceware account mkuvyrkov to glibc group?
Roland,
Would you please authorize me being added to glibc group? I'm now getting more involved with glibc development (versus previous EGLIBC development) and have several patches pending review/commit for 2.17.
Thank you,
--
Maxim Kuvyrkov
CodeSourcery / Mentor Graphics
next reply other threads:[~2012-07-02 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 18:46 Maxim Kuvyrkov [this message]
2012-07-02 19:09 ` Roland McGrath
2012-07-09 13:23 ` Ian Lance Taylor
2013-10-09 19:53 glibc " Torvald Riegel
2013-10-09 19:55 ` Frank Ch. Eigler
2019-09-25 5:12 Alistair Francis
2019-09-25 14:07 ` Christopher Faylor
2019-09-25 15:22 ` Carlos O'Donell
2019-09-25 16:24 ` Alistair Francis
2019-09-25 16:43 ` Carlos O'Donell
2019-09-25 17:50 ` Christopher Faylor
2019-09-25 20:08 ` Carlos O'Donell
2019-09-25 20:45 ` Alistair Francis
2019-09-25 21:04 ` 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=6AF787AB-0944-48F4-8DE1-B86FE092A81E@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=overseers@sourceware.org \
--cc=roland@hack.frob.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).