From: James Lemke <jwlemke@mentor.com>
To: <overseers@sourceware.org>
Subject: write access to glibc
Date: Wed, 03 Dec 2014 13:11:00 -0000 [thread overview]
Message-ID: <547CCF1E.4000209@mentor.com> (raw)
Please add me to the glibc group so I can commit my fix for BZ #17581
Thanks, Jim.
--
Jim Lemke, GNU Tools Sourcerer
Mentor Graphics / CodeSourcery
Orillia Ontario
next reply other threads:[~2014-12-01 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 13:11 James Lemke [this message]
2014-12-03 15:11 ` James Lemke
-- strict thread matches above, loose matches on Subject: below --
2012-07-12 11:28 Write " Andreas Krebbel
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=547CCF1E.4000209@mentor.com \
--to=jwlemke@mentor.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).