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. 415fcf49f32b634a13eee9f8aed242440359ef2b Date: Mon, 17 Oct 2022 13:09:19 +0000 (GMT) [thread overview] Message-ID: <20221017130919.0F6E23858D32@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 415fcf49f32b634a13eee9f8aed242440359ef2b (commit) from ece15e0758bdbb6938942a9f91f6342e66fe443a (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 415fcf49f32b634a13eee9f8aed242440359ef2b Author: Martin Liska <mliska@suse.cz> Date: Mon Oct 17 15:09:10 2022 +0200 Fix error in codingconventions.html. diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html index b059b23e..56c77555 100644 --- a/htdocs/codingconventions.html +++ b/htdocs/codingconventions.html @@ -80,7 +80,7 @@ the conventions separately from any other changes to the code.</p> </li> </ul> </li> -<li><a href="#python">Python Language Conventions</a> +<li><a href="#python">Python Language Conventions</a></li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/codingconventions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-10-17 13:09 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=20221017130919.0F6E23858D32@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).