From: Jonathan Corbet <corbet@lwn.net>
To: Doehyun Baek <doehyunbaek@gmail.com>, linux-doc@vger.kernel.org
Cc: federico.vaga@vaga.pv.it, skhan@linuxfoundation.org,
Doehyun Baek <doehyunbaek@gmail.com>
Subject: Re: [PATCH v2] Docs/translations/it_IT: update current minimal requirements
Date: Tue, 07 Jul 2026 07:23:30 -0600 [thread overview]
Message-ID: <87zf03q6gd.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260707092613.1373425-1-doehyunbaek@gmail.com>
Doehyun Baek <doehyunbaek@gmail.com> writes:
> Update the Italian minimum requirements table to match
> Documentation/process/changes.rst for Rust, bindgen, pahole, Sphinx and
> Python.
>
> Signed-off-by: Doehyun Baek <doehyunbaek@gmail.com>
> Cc: Federico Vaga <federico.vaga@vaga.pv.it>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> ---
> Changes in v2:
> - Rebase on current docs-next.
>
> Documentation/translations/it_IT/process/changes.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/translations/it_IT/process/changes.rst b/Documentation/translations/it_IT/process/changes.rst
> index 7ee54c972418..1f89bae7b6c2 100644
> --- a/Documentation/translations/it_IT/process/changes.rst
> +++ b/Documentation/translations/it_IT/process/changes.rst
> @@ -34,14 +34,14 @@ PC Card, per esempio, probabilmente non dovreste preoccuparvi di pcmciautils.
> ====================== ================= ========================================
> GNU C 8.1 gcc --version
> Clang/LLVM (optional) 17.0.1 clang --version
> -Rust (opzionale) 1.78.0 rustc --version
> -bindgen (opzionale) 0.65.1 bindgen --version
> +Rust (opzionale) 1.85.0 rustc --version
> +bindgen (opzionale) 0.71.1 bindgen --version
I don't quite understand...this text is still far removed from the
English version. If you are going to update the file, why not make it
current? Especially since you should be able to just cut and paste the
appropriate section directly from the English version?
Perhaps even better would be to find a way to include that text directly
so that we only have to maintain one version, but that can come later...
Thanks,
jon
next prev parent reply other threads:[~2026-07-07 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 9:26 [PATCH v2] Docs/translations/it_IT: update current minimal requirements Doehyun Baek
2026-07-07 13:23 ` Jonathan Corbet [this message]
2026-07-08 11:42 ` [PATCH v3] Docs/translations/it_IT: sync changes.rst requirements Doehyun Baek
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=87zf03q6gd.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=doehyunbaek@gmail.com \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=skhan@linuxfoundation.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