linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: documentation
Date: Sun, 17 May 2020 13:45:44 -0600	[thread overview]
Message-ID: <20200517134544.7d649bbb@lwn.net> (raw)
In-Reply-To: <20200516122740.30665-1-grandmaster@al2klimov.de>

On Sat, 16 May 2020 14:27:40 +0200
"Alexander A. Klimov" <grandmaster@al2klimov.de> wrote:

> ... for security reasons.
> 
> No breaking changes as either the HTTP vhost redirects to HTTPS
> or both vhosts redirect to the same location
> or both serve the same content.

We're getting closer, but...

 - There is still too much stuff here.  Remember that somebody has to look
   at and review this stuff.

 - A quick check shows that a fair number of these links are broken or
   redirect to somewhere else.  What is the value of adding "https" to a
   broken link?

 - Various documents have maintainers who are likely to be interested in
   changes and should be copied; that is what the get_maintainer.pl script
   is for.  If that generates a massive list of recipients, that's a cue
   that your patch is too large.

If you really want to push this forward, please:

 - narrow down further.  Start with, say, Documentation/maintainer and
   just do that.

 - Make sure every link you touch actually works.  If they don't, don't
   just add "https", figure out what the link should be or, if no
   applicable link exists, delete them.

 - Justify the changes in the changelog; "for security reasons" is not, by
   itself, particularly convincing.  What security threat are you
   addressing here?

Then, maybe, we'll have patches that can be reviewed and applied.

Thanks,

jon

       reply	other threads:[~2020-05-17 19:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200516122740.30665-1-grandmaster@al2klimov.de>
2020-05-17 19:45 ` Jonathan Corbet [this message]
2020-05-17 20:00   ` [PATCH] Replace HTTP links with HTTPS ones: documentation Matthew Wilcox
2020-05-17 20:18   ` Alexander A. Klimov
2020-05-19 16:10     ` Jonathan Corbet
2020-05-19 18:50       ` Alexander A. Klimov
2020-05-19 19:43         ` Jonathan Corbet
2020-05-19 20:49 ` Andy Shevchenko
2020-05-19 22:04   ` Alexander A. Klimov
2020-05-20  8:25     ` Andy Shevchenko
2020-05-20 20:00 Alexander A. Klimov
     [not found] ` <CAHZk5We1y7o+s7LG=7Q4mVynj5CvJ7RdXLx6WFd-k0yyk=DyPw@mail.gmail.com>
2020-05-22  9:18   ` Alexander A. Klimov
2020-05-25 16:28 ` Jonathan Corbet
2020-05-25 18:01   ` Alexander A. Klimov
2020-05-25 18:24     ` Joe Perches
2020-05-25 18:32       ` Alexander A. Klimov
2020-05-25 19:41     ` Jonathan Corbet
  -- strict thread matches above, loose matches on Subject: below --
2020-05-26  6:05 Alexander A. Klimov
2020-06-08 15:33 ` Jonathan Corbet

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=20200517134544.7d649bbb@lwn.net \
    --to=corbet@lwn.net \
    --cc=grandmaster@al2klimov.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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: 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 NNTP newsgroup(s).