Commit e7b4311e authored by Alexander A. Klimov's avatar Alexander A. Klimov Committed by Jonathan Corbet
Browse files

Replace HTTP links with HTTPS ones: Documentation/process 

Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.

Deterministic algorithm:
For each file:
  If not .svg:
    For each line:
      If doesn't contain `\bxmlns\b`:
        For each link, `\bhttp://[^#

 \t\r\n]*(?:\w|/)`:
          If both the HTTP and HTTPS versions
          return 200 OK and serve the same content:
            Replace HTTP with HTTPS.

Signed-off-by: default avatarAlexander A. Klimov <grandmaster@al2klimov.de>
Acked-by: default avatarMiguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Link: https://lore.kernel.org/r/20200621133630.46435-1-grandmaster@al2klimov.de


Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent c69f22f2

Documentation/process/2.Process.rst

+6 −6
Original line number Diff line number Diff line
@@ -295,7 +295,7 @@ mainline get there via -mm. 
The current -mm patch is available in the "mmotm" (-mm of the moment)

directory at:



	http://www.ozlabs.org/~akpm/mmotm/

	https://www.ozlabs.org/~akpm/mmotm/



Use of the MMOTM tree is likely to be a frustrating experience, though;

there is a definite chance that it will not even compile.
@@ -306,7 +306,7 @@ the mainline is expected to look like after the next merge window closes. 
Linux-next trees are announced on the linux-kernel and linux-next mailing

lists when they are assembled; they can be downloaded from:



	http://www.kernel.org/pub/linux/kernel/next/

	https://www.kernel.org/pub/linux/kernel/next/



Linux-next has become an integral part of the kernel development process;

all patches merged during a given merge window should really have found
@@ -365,21 +365,21 @@ to keep up with what other developers (and the mainline) are doing. 
Git is now packaged by almost all Linux distributions.  There is a home

page at:



	http://git-scm.com/

	https://git-scm.com/



That page has pointers to documentation and tutorials.



Among the kernel developers who do not use git, the most popular choice is

almost certainly Mercurial:



	http://www.selenic.com/mercurial/

	https://www.selenic.com/mercurial/



Mercurial shares many features with git, but it provides an interface which

many find easier to use.



The other tool worth knowing about is Quilt:



	http://savannah.nongnu.org/projects/quilt/

	https://savannah.nongnu.org/projects/quilt/



Quilt is a patch management system, rather than a source code management

system.  It does not track history over time; it is, instead, oriented
@@ -494,7 +494,7 @@ Andrew Morton gives this advice for aspiring kernel developers 
	with others on getting things fixed up (this can require

	persistence!) but that's fine - it's a part of kernel development.



(http://lwn.net/Articles/283982/).

(https://lwn.net/Articles/283982/).



In the absence of obvious problems to fix, developers are advised to look

at the current lists of regressions and open bugs in general.  There is

Documentation/process/4.Coding.rst

+2 −2
Original line number Diff line number Diff line
@@ -210,7 +210,7 @@ breaks? The best answer to this question was expressed by Linus in July, 
	progress at all. Is it two steps forwards, one step back, or one

	step forward and two steps back?



(http://lwn.net/Articles/243460/).

(https://lwn.net/Articles/243460/).



An especially unwelcome type of regression is any sort of change to the

user-space ABI.  Once an interface has been exported to user space, it must
@@ -323,7 +323,7 @@ other architectures. If you do not happen to have an S/390 system or a 
Blackfin development board handy, you can still perform the compilation

step.  A large set of cross compilers for x86 systems can be found at



	http://www.kernel.org/pub/tools/crosstool/

	https://www.kernel.org/pub/tools/crosstool/



Some time spent installing and using these compilers will help avoid

embarrassment later.

Documentation/process/botching-up-ioctls.rst

+1 −1
Original line number Diff line number Diff line
@@ -2,7 +2,7 @@ 
(How to avoid) Botching up ioctls

=================================



From: http://blog.ffwll.ch/2013/11/botching-up-ioctls.html

From: https://blog.ffwll.ch/2013/11/botching-up-ioctls.html



By: Daniel Vetter, Copyright © 2013 Intel Corporation

Documentation/process/changes.rst

+3 −3
Original line number Diff line number Diff line
@@ -129,7 +129,7 @@ Architectural changes 
---------------------



DevFS has been obsoleted in favour of udev

(http://www.kernel.org/pub/linux/utils/kernel/hotplug/)

(https://www.kernel.org/pub/linux/utils/kernel/hotplug/)



32-bit UID support is now in place.  Have fun!
@@ -421,7 +421,7 @@ Intel P6 microcode 
udev

----



- <http://www.freedesktop.org/software/systemd/man/udev.html>

- <https://www.freedesktop.org/software/systemd/man/udev.html>



FUSE

----
@@ -474,4 +474,4 @@ Kernel documentation 
Sphinx

------



- <http://www.sphinx-doc.org/>
 
- <https://www.sphinx-doc.org/>

Documentation/process/clang-format.rst

+1 −1
Original line number Diff line number Diff line
@@ -32,7 +32,7 @@ Linux distributions for a long time. Search for ``clang-format`` in 
your repositories. Otherwise, you can either download pre-built

LLVM/clang binaries or build the source code from:



    http://releases.llvm.org/download.html

    https://releases.llvm.org/download.html



See more information about the tool at:

CRA Git | Maintained and supported by SUSTech CRA and CCSE