From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: "Kees Cook" <keescook@chromium.org>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"David Sterba" <dsterba@suse.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
"Pankaj Bharadiya" <pankaj.laxminarayan.bharadiya@intel.com>,
"Jacob Huisman" <jacobhuisman@kernelthusiast.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Rob Herring" <robh@kernel.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>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT
Date: Thu, 11 Jun 2020 12:40:11 +0200 [thread overview]
Message-ID: <CANiq72n50OVRtFAQkAmqjaj=dJTP9VqYYHN7++8O_t4cbfaJgw@mail.gmail.com> (raw)
In-Reply-To: <8ee16c38-e28b-b4e6-ed30-55a59e216b49@al2klimov.de>
On Thu, Jun 11, 2020 at 9:02 AM Alexander A. Klimov
<grandmaster@al2klimov.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
next prev parent reply other threads:[~2020-06-11 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 20:12 [PATCH] Replace HTTP links with HTTPS ones: Documentation/translations/it_IT Alexander A. Klimov
2020-06-10 8:57 ` Federico Vaga
2020-06-10 18:11 ` Alexander A. Klimov
2020-06-11 3:12 ` Kees Cook
2020-06-11 7:01 ` Alexander A. Klimov
2020-06-11 10:40 ` Miguel Ojeda [this message]
2020-06-11 11:02 ` Alexander A. Klimov
2020-06-11 12:37 ` Miguel Ojeda
2020-06-11 13:52 ` Jonathan Corbet
2020-06-11 16:05 ` Alexander A. Klimov
2020-06-11 16:14 ` 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='CANiq72n50OVRtFAQkAmqjaj=dJTP9VqYYHN7++8O_t4cbfaJgw@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=dsterba@suse.com \
--cc=federico.vaga@vaga.pv.it \
--cc=grandmaster@al2klimov.de \
--cc=j.neuschaefer@gmx.net \
--cc=jacobhuisman@kernelthusiast.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=pankaj.laxminarayan.bharadiya@intel.com \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).