From: Jonathan Corbet <corbet@lwn.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Tony Fischetti" <tony.fischetti@gmail.com>,
"Chris Packham" <chris.packham@alliedtelesis.co.nz>,
"Mauro Carvalho Chehab" <mchehab+samsung@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Borislav Petkov" <bp@suse.de>, "Will Deacon" <will@kernel.org>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
"Joe Perches" <joe@perches.com>,
"Pankaj Bharadiya" <pankaj.laxminarayan.bharadiya@intel.com>,
"Kees Cook" <keescook@chromium.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Jacob Huisman" <jacobhuisman@kernelthusiast.com>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/process
Date: Mon, 22 Jun 2020 07:06:23 -0600 [thread overview]
Message-ID: <20200622070623.086f1623@lwn.net> (raw)
In-Reply-To: <CANiq72=Y+beqZ8Dmieo_GKbyaLN8Nf1n3bVntj_o90Cn-nADRQ@mail.gmail.com>
On Mon, 22 Jun 2020 01:43:12 +0200
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> > * The script should not be neccessary once all of my changes[1] arrive
> > in torvalds/master. Instead reviewers should say like C'mon dude, what's
> > this new plain-HTTP link doing in your patch? We have 2020! Look at e.g.
> > 93431e0607e5 .
>
> In an ideal world, yes, but that won't happen unless enforced somehow.
>
> Nevertheless, even in such a case, it would be best to have a script
> to check the entire tree from time to time.
As has been noted elsewhere, checkpatch.pl seems like the appropriate
place to make this check. As for "the entire tree"...if this job gets
completed, "git grep" should be a fine way to do that.
Thanks,
jon
next prev parent reply other threads:[~2020-06-22 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 13:36 [PATCH] Replace HTTP links with HTTPS ones: Documentation/process Alexander A. Klimov
2020-06-21 13:46 ` Miguel Ojeda
2020-06-21 14:30 ` Alexander A. Klimov
2020-06-21 17:42 ` Joe Perches
2020-06-21 18:09 ` Alexander A. Klimov
2020-06-21 23:43 ` Miguel Ojeda
2020-06-22 13:06 ` Jonathan Corbet [this message]
2020-06-22 17:03 ` Miguel Ojeda
2020-06-22 17:29 ` Joe Perches
2020-06-22 20:06 ` Miguel Ojeda
2020-06-22 20:15 ` Alexander A. Klimov
2020-06-26 17:20 ` 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=20200622070623.086f1623@lwn.net \
--to=corbet@lwn.net \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@suse.de \
--cc=chang.seok.bae@intel.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=clang-built-linux@googlegroups.com \
--cc=federico.vaga@vaga.pv.it \
--cc=geert@linux-m68k.org \
--cc=grandmaster@al2klimov.de \
--cc=j.neuschaefer@gmx.net \
--cc=jacobhuisman@kernelthusiast.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ndesaulniers@google.com \
--cc=pankaj.laxminarayan.bharadiya@intel.com \
--cc=rdunlap@infradead.org \
--cc=tony.fischetti@gmail.com \
--cc=will@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).