From: "Martin Liška" <mliska@suse.cz>
To: Gerald Pfeifer <gerald@pfeifer.com>, gcc-patches@gcc.gnu.org
Subject: Re: [committed] wwwdocs: codingconventions: Properly link to flake8
Date: Wed, 9 Nov 2022 21:53:35 +0100 [thread overview]
Message-ID: <91fd31da-1acd-7bca-ac49-f6f2abe48a49@suse.cz> (raw)
In-Reply-To: <20221101120102.DDB8833E4C@hamza.pair.com>
On 11/1/22 13:01, Gerald Pfeifer wrote:
> 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.
Makes sense, thanks!
Martin
>
> 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>
prev parent reply other threads:[~2022-11-09 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 12:01 Gerald Pfeifer
2022-11-09 20:53 ` Martin Liška [this message]
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=91fd31da-1acd-7bca-ac49-f6f2abe48a49@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/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).