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 v2] doc:it_IT: align Italian documentation
Date: Sat, 14 Nov 2020 08:58:09 +0100 [thread overview]
Message-ID: <660e3652ed5691217df429bae710da88@vaga.pv.it> (raw)
In-Reply-To: <20201113145347.01fea824@lwn.net>
On 2020-11-13 22:53, Jonathan Corbet wrote:
> On Fri, 13 Nov 2020 14:36:38 +0100
> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
>
>> Translation for the following patches
>>
>> commit 905705a8fd43 ("docs: programming-languages: refresh blurb on
>> clang support")
>> commit 5ff4aa70bf34 ("docs: submitting-patches: use :doc: for
>> references")
>> commit 030f066f677f ("docs: submitting-patches: describe preserving
>> review/test tags")
>> 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 cca73e4946c4 ("docs: Correct the release date of 5.2 stable")
>> commit c170f2eb9648 ("docs: Document cross-referencing between
>> documentation pages")
>> commit 7c8b9e3000f8 ("kernel-doc: Update "cross-referencing from rST"
>> section to use automarkup")
>> commit 27def953b63b ("docs: deprecated.rst: Expand str*cpy()
>> replacement notes")
>> commit 17dca0502314 ("docs: deprecated.rst: Update
>> zero-length/one-element arrays section")
>> commit 3519c4d6e08e ("Documentation: add minimum clang/llvm version")
>> commit 0bddd227f3dc ("Documentation: update for gcc 4.9 requirement")
>> commit 9f364b605f34 ("submitting-patches.rst: presume git will be
>> used")
>> commit 4ebdf7be21d6 ("Documentation/maintainer: rehome sign-off
>> process")
>> commit 7433ff33e8ba ("Documentation/process: expand plain-text
>> advice")
>> commit eb45fb2fb16d ("docs: process: Add cross-link to security-bugs")
>> commit bdc48fa11e46 ("checkpatch/coding-style: deprecate 80-column
>> warning")
>> commit f67281a72b30 ("Documentation: process: step 2: Link to email
>> list fixed")
>>
>> Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
>
> This doesn't apply to docs-next, not quite sure why.
I did the patch on top of the doc-next of 2 days ago. I will have a
double check.
I have other patches for new translations (4) between doc-next and this
patch. I will
try to apply it directly on doc-next.
> Also...what changed with v2? Please always include that information
> under
> the "---" line.
A missing '_'. I had a pre-compiled documentation when I did the first
build and I missed a warning.
> Thanks,
>
> jon
--
Federico Vaga
http://www.federicovaga.it/
next prev parent reply other threads:[~2020-11-14 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 13:36 [PATCH v2] doc:it_IT: align Italian documentation Federico Vaga
2020-11-13 21:53 ` Jonathan Corbet
2020-11-14 7:58 ` Federico Vaga [this message]
2022-07-02 21:08 Federico Vaga
2022-07-27 8:24 ` Federico Vaga
2022-07-28 15:37 ` Jonathan Corbet
2022-12-30 17:31 [PATCH V2] " Federico Vaga
2022-12-31 0:17 ` Akira Yokosawa
2022-12-31 13:09 ` Federico Vaga
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=660e3652ed5691217df429bae710da88@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).