From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [doc] Update Joe Buck's entry in contrib.texi
Date: Fri, 10 Apr 2015 20:56:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1504102255220.9357@tuna.site> (raw)
...as I had discussed with Joe back in fall 2013. Ahem.
Committed.
Gerald
2015-04-10 Gerald Pfeifer <gerald@pfeifer.com>
* doc/contrib.texi (Contributors): Update Joe Buck's entry.
Index: doc/contrib.texi
===================================================================
--- doc/contrib.texi (revision 221991)
+++ doc/contrib.texi (working copy)
@@ -128,7 +128,8 @@
Joerg Brunsmann for Java compiler hacking and help with the GCJ FAQ@.
@item
-Joe Buck for his direction via the steering committee.
+Joe Buck for his direction via the steering committee from its creation
+to 2013.
@item
Craig Burley for leadership of the G77 Fortran effort.
reply other threads:[~2015-04-10 20:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LSU.2.20.1504102255220.9357@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.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).