public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-6628] libstdc++: Refer to documentation hacking docs from Makefile
Date: Mon, 13 Mar 2023 10:42:30 +0000 (GMT)	[thread overview]
Message-ID: <20230313104230.C8A673858438@sourceware.org> (raw)

https://gcc.gnu.org/g:6ba33b188984badf0fc93c34af4bb640d611bd5c

commit r13-6628-g6ba33b188984badf0fc93c34af4bb640d611bd5c
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Mar 13 10:30:47 2023 +0000

    libstdc++: Refer to documentation hacking docs from Makefile
    
    libstdc++-v3/ChangeLog:
    
            * doc/Makefile.am: Add comment referring to documentation.
            * doc/Makefile.in: Regenerate.

Diff:
---
 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

                 reply	other threads:[~2023-03-13 10:42 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=20230313104230.C8A673858438@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).