From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc:it_IT: align Italian documentation
Date: Fri, 11 Sep 2020 09:36:31 +0200 [thread overview]
Message-ID: <81d39ba2d36720c9dc76a3b783799b77@vaga.pv.it> (raw)
In-Reply-To: <20200910105811.0aea6a65@lwn.net>
sure, no problem
On 2020-09-10 18:58, Jonathan Corbet wrote:
> On Thu, 10 Sep 2020 00:38:39 +0200
> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
>
>> Translation for the following patches
>>
>> commit 68e4cd17e218 ("docs: deprecated.rst: Add zero-length and
>> one-element arrays")
>> commit 5429ef62bcf3 ("compiler/gcc: Raise minimum GCC version for
>> kernel builds to 4.8")
>> commit 5b5bbb8cc51b ("docs: process: Add an example for creating a
>> fixes tag")
>> commit 858e6845654d ("docs: dt: convert submitting-patches.txt to ReST
>> format")
>> commit bdc48fa11e46 ("checkpatch/coding-style: deprecate 80-column
>> warning")
>> commit cca73e4946c4 ("docs: Correct the release date of 5.2 stable")
>>
>> Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
>
> So this doesn't apply to current docs-next...care to respin?
>
> Thanks,
>
> jon
--
Federico Vaga
http://www.federicovaga.it/
next prev parent reply other threads:[~2020-09-11 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 22:38 [PATCH] doc:it_IT: align Italian documentation Federico Vaga
2020-09-10 16:58 ` Jonathan Corbet
2020-09-11 7:36 ` Federico Vaga [this message]
2020-11-12 21:22 Federico Vaga
2021-04-09 22:41 Federico Vaga
2021-04-13 21:09 ` Jonathan Corbet
2022-06-28 11:16 Federico Vaga
2022-06-30 17:37 ` Jonathan Corbet
2022-06-30 18:20 ` Jonathan Corbet
2022-07-01 7:53 ` Federico Vaga
2022-12-30 17:25 Federico Vaga
2024-03-16 22:54 Federico Vaga
2024-05-02 13:35 ` Federico Vaga
2024-05-02 15:46 ` 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=81d39ba2d36720c9dc76a3b783799b77@vaga.pv.it \
--to=federico.vaga@vaga.pv.it \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).