From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Update my author blurb in the manual
Date: Tue, 8 Nov 2022 03:09:51 +0000 [thread overview]
Message-ID: <20221108030951.1539586-1-jwakely@redhat.com> (raw)
Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* doc/xml/authors.xml: Update the blurb listing my doc
contributions.
---
libstdc++-v3/doc/xml/authors.xml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libstdc++-v3/doc/xml/authors.xml b/libstdc++-v3/doc/xml/authors.xml
index 95626d46cba..ee8e835f692 100644
--- a/libstdc++-v3/doc/xml/authors.xml
+++ b/libstdc++-v3/doc/xml/authors.xml
@@ -102,7 +102,10 @@
<author><personname><firstname>Jonathan</firstname><surname>Wakely</surname></personname><personblurb>
<para>
- shared_ptr, markup editing and styling
+ Allocators, ABI History, API Evolution and Deprecation History,
+ Experimental Library Extensions, Implementation Status,
+ Running the Testsuite, Shared Library Versioning, Using Macros,
+ Using Exceptions, shared_ptr, markup editing and styling.
</para>
</personblurb></author>
--
2.38.1
reply other threads:[~2022-11-08 3:09 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=20221108030951.1539586-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).