Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Jonathan Corbet]

On Thu, 11 Jun 2020 18:05:37 +0200
"Alexander A. Klimov"  wrote:

> Once the doc subsystems patches get applied (or even reach 
> torvalds/master) I'll submit maybe ten patches at once. And the more 
> maintainers apply them...

The first patch is in mainline now.  I'll deal with subsequent ones after
the merge window closes.

Thanks,

jon

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Alexander A. Klimov]

Am 11.06.20 um 09:01 schrieb Alexander A. Klimov:



Am 11.06.20 um 05:12 schrieb Kees Cook:

On Wed, Jun 10, 2020 at 08:11:39PM +0200, Alexander A. Klimov wrote:

Am 10.06.20 um 10:57 schrieb Federico Vaga:

On Tuesday, June 9, 2020 10:12:41 PM CEST Alexander A. Klimov wrote:

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:
    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.


Is this script somewhere we can read it? (It's easier usually to review
the code for bulk changes than the bulk changes themselves.)

Is any of you familiar with Golang?

@Maintainers Would any of you actually review like this? If yes, is the 
pseudo-code not enough?






Signed-off-by: Alexander A. Klimov 
---
   .../translations/it_IT/admin-guide/README.rst  |  2 +-
   .../translations/it_IT/doc-guide/parse-headers.rst |  2 +-
   .../translations/it_IT/doc-guide/sphinx.rst    | 10 +-
   .../translations/it_IT/process/2.Process.rst   | 12 
++--

   .../translations/it_IT/process/3.Early-stage.rst   |  2 +-
   .../translations/it_IT/process/4.Coding.rst    |  4 ++--
   .../it_IT/process/7.AdvancedTopics.rst |  8 
   .../translations/it_IT/process/8.Conclusion.rst    | 14 
+++---

   .../translations/it_IT/process/adding-syscalls.rst |  4 ++--
   .../translations/it_IT/process/changes.rst |  6 +++---
   .../translations/it_IT/process/clang-format.rst    |  2 +-
   .../translations/it_IT/process/coding-style.rst    |  2 +-
   Documentation/translations/it_IT/process/howto.rst |  2 +-
   .../it_IT/process/maintainer-pgp-guide.rst |  2 +-
   .../it_IT/process/submitting-patches.rst   |  4 ++--
   .../it_IT/process/volatile-considered-harmful.rst  |  4 ++--
   16 files changed, 40 insertions(+), 40 deletions(-)





diff --git a/Documentation/translations/it_IT/doc-guide/sphinx.rst
b/Documentation/translations/it_IT/doc-guide/sphinx.rst index
f1ad4504b734..0aaeb0297661 100644
--- a/Documentation/translations/it_IT/doc-guide/sphinx.rst
+++ b/Documentation/translations/it_IT/doc-guide/sphinx.rst
@@ -14,7 +14,7 @@ Per generare la documentazione in HTML o PDF, usate
comandi ``make htmldocs`` o ``make pdfdocs``. La documentazione così
generata sarà disponibile nella cartella ``Documentation/output``.

-.. _Sphinx: http://www.sphinx-doc.org/
+.. _Sphinx: https://www.sphinx-doc.org/
   .. _reStructuredText: http://docutils.sourceforge.net/rst.html


It is not part of the deterministic algorithm but you may consider 
this as

well


Why did it not match?
I didn't log that link-by-link. Maybe because I also didn't follow plain 
HTTP redirects while opening HTTPS links. Maybe it even matched, but was 
added after I made the changes.


Anyway, I'll maybe cover it in round II.





-.. _reStructuredText: http://docutils.sourceforge.net/rst.html
+.. _reStructuredText: https://docutils.sourceforge.io/rst.html


I'll think about analyzing such almost-matches, extending the algo and
supplying a second round of patches once all [1] of this round arrive in
torvalds/master.

[1]:

➜  linux git:(feature/https-links-3) ✗ git diff --shortstat
  1963 files changed, 2882 insertions(+), 2882 deletions(-)
➜  linux git:(feature/https-links-3) ✗


Is there a reason to do this one language at a time instead of just
doing everything in one go?
And yes, *at the moment* I'm patching one subsystem at a time. And the 
discussion around 93431e0607e5 and all of its prototypes shown that it 
was smarter than supplying thousands of patches at once.


Now I've (hopefully) made and corrected all possible mistakes in two 
patches and clearly know how to continue with the next thousands so the 
maintainers won't have anything to comply about.


Once the doc subsystems patches get applied (or even reach 
torvalds/master) I'll submit maybe ten patches at once. And the more 
maintainers apply them...



There are two reasons:

* Jonathan said like theoretically you could give it all at once to 
Linus, but practically I'd not do that, please split by subsystem
* Linus *didn't even respond* (at least I didn't receive anything) to my 
catch-them-all patch at all, not even like please not as .gz attachment 
or please split by subsystem >

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Jonathan Corbet]

On Thu, 11 Jun 2020 13:02:08 +0200
"Alexander A. Klimov"  wrote:

> Who if not Linus shall review one huge patch spreading across lots of 
> subsystems?

In practice almost nobody, which is why I've said several times that you
shouldn't do that.  There is no flag-day situation forcing this work to be
done in a single big patch.

jon

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Miguel Ojeda]

On Thu, Jun 11, 2020 at 1:02 PM Alexander A. Klimov
 wrote:
>
> Who if not Linus shall review one huge patch spreading across lots of
> subsystems?

Even if a patch is tree-wide, ideally it is first ack'd/reviewed by
each subsystem maintainer. The overall idea is that changes are
reviewed by several people. Thus sending patches directly to Linus,
Andrew Morton, Greg K-H, etc. without previous discussion is a last
resort.

Cheers,
Miguel

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Alexander A. Klimov]

Am 11.06.20 um 12:40 schrieb Miguel Ojeda:

On Thu, Jun 11, 2020 at 9:02 AM Alexander A. Klimov
 wrote:


Is any of you familiar with Golang?


Don't worry about that! I'd expect seasoned C programmers to be able
to read Go (or near languages) -- at least to have a general idea of
what an algorithm does.

It is not APL, after all :-)

Fine.


package main

import (
"bufio"
"bytes"
"context"
"errors"
"fmt"
fatomic "github.com/natefinch/atomic"
"golang.org/x/sync/semaphore"
"io"
"io/ioutil"
"net/http"
"os"
"os/exec"
"regexp"
"runtime"
"sync"
"sync/atomic"
"time"
)

var fileSemaphore = semaphore.NewWeighted(int64(runtime.NumCPU()) * 16)
var wg sync.WaitGroup

var processingFiles = struct {
sync.RWMutex

files map[string]struct{}
}{
files: map[string]struct{}{},
}

func main() {
cmd := exec.Command("git", "ls-files", "-sz")
cmd.Stderr = os.Stderr

out, errSP := cmd.StdoutPipe()
if errSP != nil {
fmt.Fprintln(os.Stderr, errSP.Error())
os.Exit(1)
}

if errSt := cmd.Start(); errSt != nil {
fmt.Fprintln(os.Stderr, errSt.Error())
os.Exit(1)
}

//go printProcessingFiles()

buf := bufio.NewReader(out)
for {
file, errRB := buf.ReadBytes(0)
if errRB != nil && errRB != io.EOF {
if errWt := cmd.Wait(); errWt != nil {
fmt.Fprintln(os.Stderr, errWt.Error())
wg.Wait()
os.Exit(1)
}

fmt.Fprintln(os.Stderr, errRB.Error())
wg.Wait()
os.Exit(1)
}

if bytes.HasPrefix(file, []byte{'1', '0', '0'}) {
			if fields := bytes.SplitN(bytes.SplitN(file, []byte{0}, 2)[0], 
[]byte{9}, 2); len(fields) == 2 {

_ = fileSemaphore.Acquire(context.Background(), 
1)
wg.Add(1)
go processFile(string(fields[1]))
}
}

if errRB == io.EOF {
break
}
}

wg.Wait()

if errWt := cmd.Wait(); errWt != nil {
fmt.Fprintln(os.Stderr, errWt.Error())
os.Exit(1)
}
}

/*
func printProcessingFiles() {
for {
time.Sleep(time.Second)

processingFiles.RLock()
fmt.Fprintln(os.Stderr, processingFiles.files)
processingFiles.RUnlock()
}
}
*/

var httpLink = regexp.MustCompile(`\bhttp://[^# \t\r\n]*(?:\w|/)`)
var xmlns = regexp.MustCompile(`\bxmlns\b`)

func processFile(file string) error {
defer fileSemaphore.Release(1)
defer wg.Done()

processingFiles.Lock()
processingFiles.files[file] = struct{}{}
processingFiles.Unlock()

defer func() {
processingFiles.Lock()
delete(processingFiles.files, file)
processingFiles.Unlock()
}()

content, errRF := ioutil.ReadFile(file)
if errRF != nil {
return errRF
}

lines := bytes.Split(content, []byte{'\n'})
for i := range lines {
if !xmlns.Match(lines[i]) {
lines[i] = httpLink.ReplaceAllFunc(lines[i], 
processLink)
}
}

	if modified := bytes.Join(lines, []byte{'\n'}); bytes.Compare(modified, 
content) != 0 {

var buf bytes.Buffer
buf.Write(modified)
return fatomic.WriteFile(file, )
}

return nil
}

type linkOk struct {
sync.Mutex

ok uint32
}

var links = map[string]*linkOk{}
var linksLock sync.RWMutex
var notsecure = http.Client{Timeout: 10 * time.Minute}
var secure = http.Client{Timeout: 10 * time.Minute, CheckRedirect: 
httpsRedirect}


func processLink(link []byte) []byte {
linkStr := string(bytes.TrimPrefix(link, []byte("http://;)))

linksLock.RLock()
lo, ok := links[linkStr]
linksLock.RUnlock()

if !ok {
linksLock.Lock()

lo, ok = links[linkStr]
if !ok {
lo = {}
links[linkStr] = lo
}

linksLock.Unlock()
}

for {
switch atomic.LoadUint32() {
case 0:
lo.Lock()

if atomic.LoadUint32() == 0 {
if httpsAble(linkStr) {
atomic.StoreUint32(, 2)
} else {

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Miguel Ojeda]

On Thu, Jun 11, 2020 at 9:02 AM Alexander A. Klimov
 wrote:
>
> Is any of you familiar with Golang?

Don't worry about that! I'd expect seasoned C programmers to be able
to read Go (or near languages) -- at least to have a general idea of
what an algorithm does.

It is not APL, after all :-)

>
> @Maintainers Would any of you actually review like this? If yes, is the
> pseudo-code not enough?

Well, Kees already mentioned he would like to see it :-) As he said,
it is usually the way for bulk patches to present the
algorithm/semantic patch/etc. that was used.

It is also useful to have it around so that it can be reused/reapplied
later on, too.

> I didn't log that link-by-link. Maybe because I also didn't follow plain
> HTTP redirects while opening HTTPS links. Maybe it even matched, but was
> added after I made the changes.

It would be nice to have a list of links which cannot be converted,
since nowadays they are likely to be the exception rather than the
rule.

> * Linus *didn't even respond* (at least I didn't receive anything) to my
> catch-them-all patch at all, not even like please not as .gz attachment
> or please split by subsystem

Please take into account that LKML volume is huge and Linus (like
everybody else) only reads a small subset. Further, as a general rule,
Linus shouldn't be picking individual patches to begin with because
that skips the review tree.

Cheers,
Miguel

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Alexander A. Klimov]

Am 11.06.20 um 05:12 schrieb Kees Cook:

On Wed, Jun 10, 2020 at 08:11:39PM +0200, Alexander A. Klimov wrote:

Am 10.06.20 um 10:57 schrieb Federico Vaga:

On Tuesday, June 9, 2020 10:12:41 PM CEST Alexander A. Klimov wrote:

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:
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.


Is this script somewhere we can read it? (It's easier usually to review
the code for bulk changes than the bulk changes themselves.)

Is any of you familiar with Golang?

@Maintainers Would any of you actually review like this? If yes, is the 
pseudo-code not enough?






Signed-off-by: Alexander A. Klimov 
---
   .../translations/it_IT/admin-guide/README.rst  |  2 +-
   .../translations/it_IT/doc-guide/parse-headers.rst |  2 +-
   .../translations/it_IT/doc-guide/sphinx.rst| 10 +-
   .../translations/it_IT/process/2.Process.rst   | 12 ++--
   .../translations/it_IT/process/3.Early-stage.rst   |  2 +-
   .../translations/it_IT/process/4.Coding.rst|  4 ++--
   .../it_IT/process/7.AdvancedTopics.rst |  8 
   .../translations/it_IT/process/8.Conclusion.rst| 14 +++---
   .../translations/it_IT/process/adding-syscalls.rst |  4 ++--
   .../translations/it_IT/process/changes.rst |  6 +++---
   .../translations/it_IT/process/clang-format.rst|  2 +-
   .../translations/it_IT/process/coding-style.rst|  2 +-
   Documentation/translations/it_IT/process/howto.rst |  2 +-
   .../it_IT/process/maintainer-pgp-guide.rst |  2 +-
   .../it_IT/process/submitting-patches.rst   |  4 ++--
   .../it_IT/process/volatile-considered-harmful.rst  |  4 ++--
   16 files changed, 40 insertions(+), 40 deletions(-)





diff --git a/Documentation/translations/it_IT/doc-guide/sphinx.rst
b/Documentation/translations/it_IT/doc-guide/sphinx.rst index
f1ad4504b734..0aaeb0297661 100644
--- a/Documentation/translations/it_IT/doc-guide/sphinx.rst
+++ b/Documentation/translations/it_IT/doc-guide/sphinx.rst
@@ -14,7 +14,7 @@ Per generare la documentazione in HTML o PDF, usate
comandi ``make htmldocs`` o ``make pdfdocs``. La documentazione così
generata sarà disponibile nella cartella ``Documentation/output``.

-.. _Sphinx: http://www.sphinx-doc.org/
+.. _Sphinx: https://www.sphinx-doc.org/
   .. _reStructuredText: http://docutils.sourceforge.net/rst.html


It is not part of the deterministic algorithm but you may consider this as
well


Why did it not match?
I didn't log that link-by-link. Maybe because I also didn't follow plain 
HTTP redirects while opening HTTPS links. Maybe it even matched, but was 
added after I made the changes.


Anyway, I'll maybe cover it in round II.





-.. _reStructuredText: http://docutils.sourceforge.net/rst.html
+.. _reStructuredText: https://docutils.sourceforge.io/rst.html


I'll think about analyzing such almost-matches, extending the algo and
supplying a second round of patches once all [1] of this round arrive in
torvalds/master.

[1]:

➜  linux git:(feature/https-links-3) ✗ git diff --shortstat
  1963 files changed, 2882 insertions(+), 2882 deletions(-)
➜  linux git:(feature/https-links-3) ✗


Is there a reason to do this one language at a time instead of just
doing everything in one go?

There are two reasons:

* Jonathan said like theoretically you could give it all at once to 
Linus, but practically I'd not do that, please split by subsystem
* Linus *didn't even respond* (at least I didn't receive anything) to my 
catch-them-all patch at all, not even like please not as .gz attachment 
or please split by subsystem

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Kees Cook]

On Wed, Jun 10, 2020 at 08:11:39PM +0200, Alexander A. Klimov wrote:
> Am 10.06.20 um 10:57 schrieb Federico Vaga:
> > On Tuesday, June 9, 2020 10:12:41 PM CEST Alexander A. Klimov wrote:
> > > 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:
> > >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.

Is this script somewhere we can read it? (It's easier usually to review
the code for bulk changes than the bulk changes themselves.)

> > > 
> > > Signed-off-by: Alexander A. Klimov 
> > > ---
> > >   .../translations/it_IT/admin-guide/README.rst  |  2 +-
> > >   .../translations/it_IT/doc-guide/parse-headers.rst |  2 +-
> > >   .../translations/it_IT/doc-guide/sphinx.rst| 10 +-
> > >   .../translations/it_IT/process/2.Process.rst   | 12 ++--
> > >   .../translations/it_IT/process/3.Early-stage.rst   |  2 +-
> > >   .../translations/it_IT/process/4.Coding.rst|  4 ++--
> > >   .../it_IT/process/7.AdvancedTopics.rst |  8 
> > >   .../translations/it_IT/process/8.Conclusion.rst| 14 +++---
> > >   .../translations/it_IT/process/adding-syscalls.rst |  4 ++--
> > >   .../translations/it_IT/process/changes.rst |  6 +++---
> > >   .../translations/it_IT/process/clang-format.rst|  2 +-
> > >   .../translations/it_IT/process/coding-style.rst|  2 +-
> > >   Documentation/translations/it_IT/process/howto.rst |  2 +-
> > >   .../it_IT/process/maintainer-pgp-guide.rst |  2 +-
> > >   .../it_IT/process/submitting-patches.rst   |  4 ++--
> > >   .../it_IT/process/volatile-considered-harmful.rst  |  4 ++--
> > >   16 files changed, 40 insertions(+), 40 deletions(-)
> > > 
> > 
> > 
> > > diff --git a/Documentation/translations/it_IT/doc-guide/sphinx.rst
> > > b/Documentation/translations/it_IT/doc-guide/sphinx.rst index
> > > f1ad4504b734..0aaeb0297661 100644
> > > --- a/Documentation/translations/it_IT/doc-guide/sphinx.rst
> > > +++ b/Documentation/translations/it_IT/doc-guide/sphinx.rst
> > > @@ -14,7 +14,7 @@ Per generare la documentazione in HTML o PDF, usate
> > > comandi ``make htmldocs`` o ``make pdfdocs``. La documentazione così
> > > generata sarà disponibile nella cartella ``Documentation/output``.
> > > 
> > > -.. _Sphinx: http://www.sphinx-doc.org/
> > > +.. _Sphinx: https://www.sphinx-doc.org/
> > >   .. _reStructuredText: http://docutils.sourceforge.net/rst.html
> > 
> > It is not part of the deterministic algorithm but you may consider this as
> > well

Why did it not match?

> > 
> > -.. _reStructuredText: http://docutils.sourceforge.net/rst.html
> > +.. _reStructuredText: https://docutils.sourceforge.io/rst.html
> > 
> I'll think about analyzing such almost-matches, extending the algo and
> supplying a second round of patches once all [1] of this round arrive in
> torvalds/master.
> 
> [1]:
> 
> ➜  linux git:(feature/https-links-3) ✗ git diff --shortstat
>  1963 files changed, 2882 insertions(+), 2882 deletions(-)
> ➜  linux git:(feature/https-links-3) ✗

Is there a reason to do this one language at a time instead of just
doing everything in one go?

-- 
Kees Cook

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Alexander A. Klimov]

Am 10.06.20 um 10:57 schrieb Federico Vaga:

On Tuesday, June 9, 2020 10:12:41 PM CEST Alexander A. Klimov wrote:

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:
   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: Alexander A. Klimov 
---
  .../translations/it_IT/admin-guide/README.rst  |  2 +-
  .../translations/it_IT/doc-guide/parse-headers.rst |  2 +-
  .../translations/it_IT/doc-guide/sphinx.rst| 10 +-
  .../translations/it_IT/process/2.Process.rst   | 12 ++--
  .../translations/it_IT/process/3.Early-stage.rst   |  2 +-
  .../translations/it_IT/process/4.Coding.rst|  4 ++--
  .../it_IT/process/7.AdvancedTopics.rst |  8 
  .../translations/it_IT/process/8.Conclusion.rst| 14 +++---
  .../translations/it_IT/process/adding-syscalls.rst |  4 ++--
  .../translations/it_IT/process/changes.rst |  6 +++---
  .../translations/it_IT/process/clang-format.rst|  2 +-
  .../translations/it_IT/process/coding-style.rst|  2 +-
  Documentation/translations/it_IT/process/howto.rst |  2 +-
  .../it_IT/process/maintainer-pgp-guide.rst |  2 +-
  .../it_IT/process/submitting-patches.rst   |  4 ++--
  .../it_IT/process/volatile-considered-harmful.rst  |  4 ++--
  16 files changed, 40 insertions(+), 40 deletions(-)





diff --git a/Documentation/translations/it_IT/doc-guide/sphinx.rst
b/Documentation/translations/it_IT/doc-guide/sphinx.rst index
f1ad4504b734..0aaeb0297661 100644
--- a/Documentation/translations/it_IT/doc-guide/sphinx.rst
+++ b/Documentation/translations/it_IT/doc-guide/sphinx.rst
@@ -14,7 +14,7 @@ Per generare la documentazione in HTML o PDF, usate
comandi ``make htmldocs`` o ``make pdfdocs``. La documentazione così
generata sarà disponibile nella cartella ``Documentation/output``.

-.. _Sphinx: http://www.sphinx-doc.org/
+.. _Sphinx: https://www.sphinx-doc.org/
  .. _reStructuredText: http://docutils.sourceforge.net/rst.html


It is not part of the deterministic algorithm but you may consider this as
well

-.. _reStructuredText: http://docutils.sourceforge.net/rst.html
+.. _reStructuredText: https://docutils.sourceforge.io/rst.html




I'll think about analyzing such almost-matches, extending the algo and 
supplying a second round of patches once all [1] of this round arrive in 
torvalds/master.


[1]:

➜  linux git:(feature/https-links-3) ✗ git diff --shortstat
 1963 files changed, 2882 insertions(+), 2882 deletions(-)
➜  linux git:(feature/https-links-3) ✗

Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Federico Vaga]

On Tuesday, June 9, 2020 10:12:41 PM CEST Alexander A. Klimov wrote:
> 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:
>   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: Alexander A. Klimov 
> ---
>  .../translations/it_IT/admin-guide/README.rst  |  2 +-
>  .../translations/it_IT/doc-guide/parse-headers.rst |  2 +-
>  .../translations/it_IT/doc-guide/sphinx.rst| 10 +-
>  .../translations/it_IT/process/2.Process.rst   | 12 ++--
>  .../translations/it_IT/process/3.Early-stage.rst   |  2 +-
>  .../translations/it_IT/process/4.Coding.rst|  4 ++--
>  .../it_IT/process/7.AdvancedTopics.rst |  8 
>  .../translations/it_IT/process/8.Conclusion.rst| 14 +++---
>  .../translations/it_IT/process/adding-syscalls.rst |  4 ++--
>  .../translations/it_IT/process/changes.rst |  6 +++---
>  .../translations/it_IT/process/clang-format.rst|  2 +-
>  .../translations/it_IT/process/coding-style.rst|  2 +-
>  Documentation/translations/it_IT/process/howto.rst |  2 +-
>  .../it_IT/process/maintainer-pgp-guide.rst |  2 +-
>  .../it_IT/process/submitting-patches.rst   |  4 ++--
>  .../it_IT/process/volatile-considered-harmful.rst  |  4 ++--
>  16 files changed, 40 insertions(+), 40 deletions(-)
> 


> diff --git a/Documentation/translations/it_IT/doc-guide/sphinx.rst
> b/Documentation/translations/it_IT/doc-guide/sphinx.rst index
> f1ad4504b734..0aaeb0297661 100644
> --- a/Documentation/translations/it_IT/doc-guide/sphinx.rst
> +++ b/Documentation/translations/it_IT/doc-guide/sphinx.rst
> @@ -14,7 +14,7 @@ Per generare la documentazione in HTML o PDF, usate
> comandi ``make htmldocs`` o ``make pdfdocs``. La documentazione così
> generata sarà disponibile nella cartella ``Documentation/output``.
> 
> -.. _Sphinx: http://www.sphinx-doc.org/
> +.. _Sphinx: https://www.sphinx-doc.org/
>  .. _reStructuredText: http://docutils.sourceforge.net/rst.html

It is not part of the deterministic algorithm but you may consider this as 
well

-.. _reStructuredText: http://docutils.sourceforge.net/rst.html
+.. _reStructuredText: https://docutils.sourceforge.io/rst.html

[PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

[Alexander A. Klimov]

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:
  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: Alexander A. Klimov 
---
 .../translations/it_IT/admin-guide/README.rst  |  2 +-
 .../translations/it_IT/doc-guide/parse-headers.rst |  2 +-
 .../translations/it_IT/doc-guide/sphinx.rst| 10 +-
 .../translations/it_IT/process/2.Process.rst   | 12 ++--
 .../translations/it_IT/process/3.Early-stage.rst   |  2 +-
 .../translations/it_IT/process/4.Coding.rst|  4 ++--
 .../it_IT/process/7.AdvancedTopics.rst |  8 
 .../translations/it_IT/process/8.Conclusion.rst| 14 +++---
 .../translations/it_IT/process/adding-syscalls.rst |  4 ++--
 .../translations/it_IT/process/changes.rst |  6 +++---
 .../translations/it_IT/process/clang-format.rst|  2 +-
 .../translations/it_IT/process/coding-style.rst|  2 +-
 Documentation/translations/it_IT/process/howto.rst |  2 +-
 .../it_IT/process/maintainer-pgp-guide.rst |  2 +-
 .../it_IT/process/submitting-patches.rst   |  4 ++--
 .../it_IT/process/volatile-considered-harmful.rst  |  4 ++--
 16 files changed, 40 insertions(+), 40 deletions(-)

diff --git a/Documentation/translations/it_IT/admin-guide/README.rst 
b/Documentation/translations/it_IT/admin-guide/README.rst
index b37166817842..fb0c0b0fde71 100644
--- a/Documentation/translations/it_IT/admin-guide/README.rst
+++ b/Documentation/translations/it_IT/admin-guide/README.rst
@@ -4,7 +4,7 @@
 
 .. _it_readme:
 
-Rilascio del kernel Linux  5.x 
+Rilascio del kernel Linux  5.x 
 ===
 
 .. warning::
diff --git a/Documentation/translations/it_IT/doc-guide/parse-headers.rst 
b/Documentation/translations/it_IT/doc-guide/parse-headers.rst
index 993d549ee2b8..e210bbd84fb6 100644
--- a/Documentation/translations/it_IT/doc-guide/parse-headers.rst
+++ b/Documentation/translations/it_IT/doc-guide/parse-headers.rst
@@ -190,7 +190,7 @@ COPYRIGHT
 
 Copyright (c) 2016 by Mauro Carvalho Chehab .
 
-Licenza GPLv2: GNU GPL version 2 .
+Licenza GPLv2: GNU GPL version 2 .
 
 Questo è software libero: siete liberi di cambiarlo e ridistribuirlo.
 Non c'è alcuna garanzia, nei limiti permessi dalla legge.
diff --git a/Documentation/translations/it_IT/doc-guide/sphinx.rst 
b/Documentation/translations/it_IT/doc-guide/sphinx.rst
index f1ad4504b734..0aaeb0297661 100644
--- a/Documentation/translations/it_IT/doc-guide/sphinx.rst
+++ b/Documentation/translations/it_IT/doc-guide/sphinx.rst
@@ -14,7 +14,7 @@ Per generare la documentazione in HTML o PDF, usate comandi 
``make htmldocs`` o
 ``make pdfdocs``. La documentazione così generata sarà disponibile nella
 cartella ``Documentation/output``.
 
-.. _Sphinx: http://www.sphinx-doc.org/
+.. _Sphinx: https://www.sphinx-doc.org/
 .. _reStructuredText: http://docutils.sourceforge.net/rst.html
 
 I file reStructuredText possono contenere delle direttive che permettono di
@@ -191,8 +191,8 @@ informazione circa le loro potenzialità. In particolare, il
 cui cominciare. Esistono, inoltre, anche alcuni
 `costruttori specifici per Sphinx`_.
 
-.. _`manuale introduttivo a reStructuredText`: 
http://www.sphinx-doc.org/en/stable/rest.html
-.. _`costruttori specifici per Sphinx`: 
http://www.sphinx-doc.org/en/stable/markup/index.html
+.. _`manuale introduttivo a reStructuredText`: 
https://www.sphinx-doc.org/en/stable/rest.html
+.. _`costruttori specifici per Sphinx`: 
https://www.sphinx-doc.org/en/stable/markup/index.html
 
 Guide linea per la documentazione del kernel
 
@@ -388,8 +388,8 @@ formato SVG::
 Le direttive del kernel per figure ed immagini supportano il formato **DOT**,
 per maggiori informazioni
 
-* DOT: http://graphviz.org/pdf/dotguide.pdf
-* Graphviz: http://www.graphviz.org/content/dot-language
+* DOT: https://graphviz.org/pdf/dotguide.pdf
+* Graphviz: https://www.graphviz.org/content/dot-language
 
 Un piccolo esempio (:ref:`it_hello_dot_file`)::
 
diff --git a/Documentation/translations/it_IT/process/2.Process.rst 
b/Documentation/translations/it_IT/process/2.Process.rst
index 30dc172f06b0..c2f3a0647d1b 100644
--- a/Documentation/translations/it_IT/process/2.Process.rst
+++ b/Documentation/translations/it_IT/process/2.Process.rst
@@ -315,7 +315,7 @@ patch andrà nel ramo principale attraverso -mm.
 La patch -mm correnti sono disponibili nella cartella "mmotm" (-mm of
 the moment) all'indirizzo:
 
-  http://www.ozlabs.org/~akpm/mmotm/
+  https://www.ozlabs.org/~akpm/mmotm/
 
 È molto