From: Thorsten Scherer <t.scherer@eckelmann.de>
To: Federico Vaga <federico.vaga@vaga.pv.it>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, Thorsten Scherer <t.scherer@eckelmann.de>
Subject: [PATCH] doc:it_IT: Fix typo in Reviewed-by tag
Date: Tue, 25 Jun 2024 23:04:53 +0200 [thread overview]
Message-ID: <20240625210455.13262-1-t.scherer@eckelmann.de> (raw)
Signed-off-by: Thorsten Scherer <t.scherer@eckelmann.de>
---
Documentation/translations/it_IT/process/7.AdvancedTopics.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/it_IT/process/7.AdvancedTopics.rst b/Documentation/translations/it_IT/process/7.AdvancedTopics.rst
index a83fcfe18024..b3d8b62f3b57 100644
--- a/Documentation/translations/it_IT/process/7.AdvancedTopics.rst
+++ b/Documentation/translations/it_IT/process/7.AdvancedTopics.rst
@@ -200,7 +200,7 @@ all'ABI dello spazio utente, eccetera. Qualunque tipo di revisione è ben
accetta e di valore, se porta ad avere un codice migliore nel kernel.
Non esistono requisiti particolarmente stringenti per l'uso di etichette come
-``Reviewd-by``. Tuttavia, perché la revisione sia efficace ci si aspetta un
+``Reviewed-by``. Tuttavia, perché la revisione sia efficace ci si aspetta un
qualche tipo di messaggio che dica "ho verificato A, B e C nel codice che è
appena stato inviato e mi sembra tutto in ordine". Inoltre, questo permette ai
manutentori di prendere conoscenza circa una revisione avvenuta per davvero.
--
2.43.0
next reply other threads:[~2024-06-25 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 21:04 Thorsten Scherer [this message]
2024-06-26 15:31 ` [PATCH] doc:it_IT: Fix typo in Reviewed-by tag Federico Vaga
2024-06-26 22:23 ` 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=20240625210455.13262-1-t.scherer@eckelmann.de \
--to=t.scherer@eckelmann.de \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.