From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: Sandra Loosemore <sandra.loosemore@siemens.com>,
Jonny Grant <jg@jguk.org>
Subject: [committed] libstdc++: Refer to documentation hacking docs from Makefile
Date: Mon, 13 Mar 2023 10:46:07 +0000 [thread overview]
Message-ID: <20230313104607.2545130-1-jwakely@redhat.com> (raw)
In-Reply-To: <CACb0b4mRPssHzGahg0rQQHMgjm0yv6Kmc1btE5g8HKo+27E-BQ@mail.gmail.com>
I've pushed this to trunk, so that it's easier to find the docs on
maintaining the docs.
-- >8 --
pick fdcba7a9088 libstdc++: Update copyright year in FAQ
pick 6d8325681ef libstdc++: Regenerate HTML docs
libstdc++-v3/ChangeLog:
* doc/Makefile.am: Add comment referring to documentation.
* doc/Makefile.in: Regenerate.
---
libstdc++-v3/doc/Makefile.am | 2 ++
libstdc++-v3/doc/Makefile.in | 2 ++
2 files changed, 4 insertions(+)
diff --git a/libstdc++-v3/doc/Makefile.am b/libstdc++-v3/doc/Makefile.am
index cc18b61cf55..8371441c62e 100644
--- a/libstdc++-v3/doc/Makefile.am
+++ b/libstdc++-v3/doc/Makefile.am
@@ -24,6 +24,8 @@ include $(top_srcdir)/fragment.am
# Documentation Overview
#
+# See ./xml/manual/documentation_hacking.xml for full details.
+#
# There are two main input materials for libstdc++ documentation.
# The first is the doxygen markup in libstdc++ sources, which is a
# reference to the API. And the second is the manual, via docbook markup in
diff --git a/libstdc++-v3/doc/Makefile.in b/libstdc++-v3/doc/Makefile.in
index db5e81a7d60..21ad8557f7a 100644
--- a/libstdc++-v3/doc/Makefile.in
+++ b/libstdc++-v3/doc/Makefile.in
@@ -393,6 +393,8 @@ AM_CPPFLAGS = $(GLIBCXX_INCLUDES) $(CPPFLAGS)
# Documentation Overview
#
+# See ./xml/manual/documentation_hacking.xml for full details.
+#
# There are two main input materials for libstdc++ documentation.
# The first is the doxygen markup in libstdc++ sources, which is a
# reference to the API. And the second is the manual, via docbook markup in
--
2.39.2
next prev parent reply other threads:[~2023-03-13 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 23:08 [PATCH] update copyright year in libstdc++ manual Jonny Grant
2023-03-12 18:46 ` Sandra Loosemore
2023-03-12 20:48 ` Jonathan Wakely
2023-03-13 10:46 ` Jonathan Wakely [this message]
2023-03-13 10:43 ` Jonathan Wakely
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=20230313104607.2545130-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jg@jguk.org \
--cc=libstdc++@gcc.gnu.org \
--cc=sandra.loosemore@siemens.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).