public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. e8afc930bc6cd9057c27b0752061ba478c692f80 Date: Wed, 9 Nov 2022 20:51:53 +0000 (GMT) [thread overview] Message-ID: <20221109205153.9CAF33858D1E@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 e8afc930bc6cd9057c27b0752061ba478c692f80 (commit) from f99e457c14cdd68eca8c66b7806cb24aed5dc245 (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 e8afc930bc6cd9057c27b0752061ba478c692f80 Author: Martin Liska <mliska@suse.cz> Date: Wed Nov 9 21:51:42 2022 +0100 remove trailing " diff --git a/htdocs/onlinedocs/index.html b/htdocs/onlinedocs/index.html index 3410f731..6cc0bd17 100644 --- a/htdocs/onlinedocs/index.html +++ b/htdocs/onlinedocs/index.html @@ -1582,7 +1582,7 @@ existing release.</p> (<a href="https://gcc.gnu.org/onlinedocs/gnat_rm.pdf">also in PDF</a>) </li> <li> - <a href="https://gcc.gnu.org/onlinedocs/gnat_ugn/">GNAT User's Guide for Native Platforms"</a> + <a href="https://gcc.gnu.org/onlinedocs/gnat_ugn/">GNAT User's Guide for Native Platforms</a> (<a href="https://gcc.gnu.org/onlinedocs/gnat_ugn.pdf">also in PDF</a>) </li> <li> ----------------------------------------------------------------------- Summary of changes: htdocs/onlinedocs/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-11-09 20:51 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=20221109205153.9CAF33858D1E@sourceware.org \ --to=marxin@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).