From: Doehyun Baek <doehyunbaek@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Doehyun Baek <doehyunbaek@gmail.com>
Subject: [PATCH] Docs/translations/it_IT: update current minimal requirements
Date: Wed, 17 Jun 2026 08:53:05 +0000 [thread overview]
Message-ID: <20260617085305.3205822-1-doehyunbaek@gmail.com> (raw)
Update the Italian translation of the current minimal requirements table to
match Documentation/process/changes.rst. The translated table still listed
older versions 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>
---
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
GNU make 4.0 make --version
bash 4.2 bash --version
binutils 2.30 ld -v
flex 2.5.35 flex --version
bison 2.0 bison --version
-pahole 1.16 pahole --version
+pahole 1.26 pahole --version
util-linux 2.10o mount --version
kmod 13 depmod -V
e2fsprogs 1.41.4 e2fsck -V
@@ -60,12 +60,12 @@ mcelog 0.6 mcelog --version
iptables 1.4.2 iptables -V
openssl & libcrypto 1.0.0 openssl version
bc 1.06.95 bc --version
-Sphinx\ [#f1]_ 2.4.4 sphinx-build --version
+Sphinx\ [#f1]_ 3.4.3 sphinx-build --version
cpio any cpio --version
GNU tar 1.28 tar --version
gtags (opzionale) 6.6.5 gtags --version
mkimage (opzionale) 2017.01 mkimage --version
-Python (opzionale) 3.5.x python3 --version
+Python (opzionale) 3.9.x python3 --version
====================== ================= ========================================
.. [#f1] Sphinx è necessario solo per produrre la documentazione del Kernel
--
2.43.0
next reply other threads:[~2026-06-17 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 8:53 Doehyun Baek [this message]
2026-06-17 13:43 ` [PATCH] Docs/translations/it_IT: update current minimal requirements 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=20260617085305.3205822-1-doehyunbaek@gmail.com \
--to=doehyunbaek@gmail.com \
--cc=corbet@lwn.net \
--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