linux-kernel - Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72n50OVRtFAQkAmqjaj=dJTP9VqYYHN7++8O_t4cbfaJgw@mail.gmail.com>
Date:   Thu, 11 Jun 2020 12:40:11 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     "Alexander A. Klimov" <grandmaster@...klimov.de>
Cc:     Kees Cook <keescook@...omium.org>,
        Federico Vaga <federico.vaga@...a.pv.it>,
        Jonathan Corbet <corbet@....net>,
        Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        David Sterba <dsterba@...e.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        "Theodore Ts'o" <tytso@....edu>,
        "Darrick J. Wong" <darrick.wong@...cle.com>,
        Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@...el.com>,
        Jacob Huisman <jacobhuisman@...nelthusiast.com>,
        Jonathan Neuschäfer <j.neuschaefer@....net>,
        Rob Herring <robh@...nel.org>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        clang-built-linux <clang-built-linux@...glegroups.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT

On Thu, Jun 11, 2020 at 9:02 AM Alexander A. Klimov
<grandmaster@...klimov.de> 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