From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, "Martin Liška" <mliska@suse.cz>
Subject: [committed] wwwdocs: codingconventions: Properly link to flake8
Date: Tue, 1 Nov 2022 13:01:00 +0100 (CET) [thread overview]
Message-ID: <20221101120102.DDB8833E4C@hamza.pair.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=X-UNKNOWN, Size: 1003 bytes --]
Nearly all hrefs= on our site are https:// or http://, and that's the case
pretty much across the web. Still the protocol needs to be provided for
links to work.
Pushed.
Gerald
Web links need to be prefixed by https:// or http://.
---
htdocs/codingconventions.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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="https://peps.python.org/pep-0008/">PEP 8 ??? Style Guide for Python Code</a>
-which can be verified by the <a href="flake8.pycqa.org">flake8</a> tool.
+which can be verified by the <a href="https://flake8.pycqa.org">flake8</a> tool.
We recommend using the following <code>flake8</code> plug-ins:</p>
<ul>
--
2.38.0
next reply other threads:[~2022-11-01 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 12:01 Gerald Pfeifer [this message]
2022-11-09 20:53 ` Martin Liška
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=20221101120102.DDB8833E4C@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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: 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).