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 r14-10129] libstdc++: Rename man pages to use '::' instead of '_' Date: Thu, 25 Apr 2024 17:44:11 +0000 (GMT) [thread overview] Message-ID: <20240425174411.BB4AF3858403@sourceware.org> (raw) https://gcc.gnu.org/g:8d80e3c5a641556e32fdf3637f08a0648f5aaab3 commit r14-10129-g8d80e3c5a641556e32fdf3637f08a0648f5aaab3 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Apr 25 14:02:36 2024 +0100 libstdc++: Rename man pages to use '::' instead of '_' The Doxygen-generated man pages for some new types need to be renamed to use '::' instead of '_' in the filenames. libstdc++-v3/ChangeLog: * scripts/run_doxygen: Rename man pages for nested types. Diff: --- libstdc++-v3/scripts/run_doxygen | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/libstdc++-v3/scripts/run_doxygen b/libstdc++-v3/scripts/run_doxygen index ea9bcb56553..11f24b058af 100644 --- a/libstdc++-v3/scripts/run_doxygen +++ b/libstdc++-v3/scripts/run_doxygen @@ -415,8 +415,21 @@ for f in __cxxabiv1_*; do mv $f $newname done +mv std::__unspecified___exception_ptr.3 std::exception_ptr.3 + # Then piecemeal nested classes +for f in std*distribution_param_type.3; do + newname=`echo $f | sed 's/distribution_param_type/distribution::param_type/'` + mv $f $newname +done + +for f in std*filesystem::path_iterator.3; do + newname=`echo $f | sed 's/path_iterator/path::iterator/'` + mv $f $newname +done + +mv std::chrono::tzdb_list_const_iterator.3 std::chrono::tzdb_list::const_iterator.3 # Generic removal bits, where there are things in the generated man # pages that need to be killed.
reply other threads:[~2024-04-25 17:44 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=20240425174411.BB4AF3858403@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: linkBe 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).