From: Jonathan Corbet <corbet@lwn.net>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: "Kees Cook" <keescook@chromium.org>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"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@vger.kernel.org, linux-kernel@vger.kernel.org,
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 10:14:18 -0600 [thread overview]
Message-ID: <20200611101418.40847b63@lwn.net> (raw)
In-Reply-To: <4196faa9-64d3-481b-9c15-bb4abb237c18@al2klimov.de>
On Thu, 11 Jun 2020 18:05:37 +0200
"Alexander A. Klimov" <grandmaster@al2klimov.de> 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
prev parent reply other threads:[~2020-06-11 16:14 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
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 [this message]
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=20200611101418.40847b63@lwn.net \
--to=corbet@lwn.net \
--cc=clang-built-linux@googlegroups.com \
--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).