public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-6355] libgomp: Avoid bad "up" link in libgomp docs Date: Mon, 28 Dec 2020 22:53:55 +0000 (GMT) [thread overview] Message-ID: <20201228225355.956AB3854808@sourceware.org> (raw) https://gcc.gnu.org/g:c33fd1607628f622a523344dbbf3afbf25b3e122 commit r11-6355-gc33fd1607628f622a523344dbbf3afbf25b3e122 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon Dec 28 23:42:45 2020 +0100 libgomp: Avoid bad "up" link in libgomp docs The libgomp texinfo docs lead to an invalid "up" link on the Top node, which we can avoid similarly to the Top link in the main GCC manual. 2020-12-28 Sandra Loosemore <sandra@codesourcery.com> libgomp/ * libgomp.texi (Top): Avoid bad "up" link. Diff: --- libgomp/libgomp.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi index 473b191ae14..9e486c7d159 100644 --- a/libgomp/libgomp.texi +++ b/libgomp/libgomp.texi @@ -68,7 +68,7 @@ Boston, MA 02110-1301, USA@* @page -@node Top +@node Top, Enabling OpenMP @top Introduction @cindex Introduction
reply other threads:[~2020-12-28 22:53 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=20201228225355.956AB3854808@sourceware.org \ --to=gerald@gcc.gnu.org \ --cc=gcc-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).