public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. 51c463bda3970547655de40b7f2604072c879dc6
Date: Tue,  1 Nov 2022 11:59:42 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

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  51c463bda3970547655de40b7f2604072c879dc6 (commit)
      from  4e2d72b4f3f7b79e194e17722207a233971210f0 (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 51c463bda3970547655de40b7f2604072c879dc6
Author: Gerald Pfeifer <>
Date:   Tue Nov 1 12:58:56 2022 +0100

    codingconventions: Properly link to flake8
    Web links need to be prefixed by https:// or http://.

diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index f5e22983..348f1e1d 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -1487,7 +1487,7 @@ Definitions within the body of a namespace are not indented.
 <h2 id="python">Python Language Conventions</h2>
 <p>Python scripts should follow <a href="">PEP 8 – Style Guide for Python Code</a>
-which can be verified by the <a href="">flake8</a> tool.
+which can be verified by the <a href="">flake8</a> tool.
 We recommend using the following <code>flake8</code> plug-ins:</p>


Summary of changes:
 htdocs/codingconventions.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


                 reply	other threads:[~2022-11-01 11:59 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be 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).