From: Jonathan Corbet <corbet@lwn.net>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] doc:it_IT: add translation for botching-up-ioctl.rst
Date: Wed, 11 Jan 2023 16:03:37 -0700 [thread overview]
Message-ID: <87zgaovfli.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230102183716.9698-1-federico.vaga@vaga.pv.it>
Federico Vaga <federico.vaga@vaga.pv.it> writes:
> This patch adds the translation for the botching up ioctl document.
>
> Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
> ---
> V1 -> V2 use the kernel-doc mecanism to link functions in documents
>
> .../it_IT/process/botching-up-ioctls.rst | 249 ++++++++++++++++++
> .../translations/it_IT/process/index.rst | 1 +
> 2 files changed, 250 insertions(+)
> create mode 100644 Documentation/translations/it_IT/process/botching-up-ioctls.rst
I've applied this, but I have to ask:
> diff --git a/Documentation/translations/it_IT/process/botching-up-ioctls.rst b/Documentation/translations/it_IT/process/botching-up-ioctls.rst
> new file mode 100644
> index 000000000000..91732cdf808a
> --- /dev/null
> +++ b/Documentation/translations/it_IT/process/botching-up-ioctls.rst
> @@ -0,0 +1,249 @@
> +.. include:: ../disclaimer-ita.rst
> +
> +:Original: Documentation/process/botching-up-ioctls.rst
> +
> +==========================================
> +(Come evitare di) Raffazzonare delle ioctl
> +==========================================
Is "raffazzonare" the right verb here? Something like "pasticciare"
seems closer to me, but I'm not the expert here.
Thanks,
jon
next prev parent reply other threads:[~2023-01-11 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 18:37 Federico Vaga
2023-01-11 23:03 ` Jonathan Corbet [this message]
2023-01-12 20:06 ` 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=87zgaovfli.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--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
all inboxes | Powered by JetHome®