public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 2f71b2d44604600e18d476032b2c2c01da9ce4d8 Date: Tue, 31 Jan 2023 22:52:38 +0000 (GMT) [thread overview] Message-ID: <20230131225238.D57293858D38@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 2f71b2d44604600e18d476032b2c2c01da9ce4d8 (commit) from 0f14b833324cb74279632a8e9904311d9ddd6cc4 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 2f71b2d44604600e18d476032b2c2c01da9ce4d8 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Tue Jan 31 23:52:19 2023 +0100 gcc-5: Fix deep link into GDB manual diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html index 893e35de..201a039f 100644 --- a/htdocs/gcc-5/changes.html +++ b/htdocs/gcc-5/changes.html @@ -504,7 +504,7 @@ version 2 and the current setting.</li> </li> <li>New random number distributions <code>logistic_distribution</code> and <code>uniform_on_sphere_distribution</code> as extensions.</li> - <li><a href="https://sourceware.org/gdb/current/onlinedocs/gdb/Xmethods-In-Python.html">GDB + <li><a href="https://sourceware.org/gdb/current/onlinedocs/gdb#Xmethods-In-Python">GDB Xmethods</a> for containers and <code>std::unique_ptr</code>.</li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-5/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-01-31 22:52 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=20230131225238.D57293858D38@sourceware.org \ --to=gerald@sourceware.org \ --cc=gcc-cvs-wwwdocs@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).