From: Jonathan Corbet <corbet@lwn.net>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Andi Shyti <andi.shyti@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
workflows@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] Doc:it_IT: Do not reference kernel.h anymore
Date: Tue, 23 Dec 2025 14:34:29 -0700 [thread overview]
Message-ID: <87h5tgubkq.fsf@trenco.lwn.net> (raw)
In-Reply-To: <b5niunhlqabuekgmsf4xrhqntx6qwi44mh7smntocomfjhoadk@fazjt4uqiv4w>
Federico Vaga <federico.vaga@vaga.pv.it> writes:
>>I'm unconvinced about "file di intestazione" based on my own
>>understanding of the language... but, in a case like this, I will defer
>>to the creator and maintainer of the translation.
>
> Due to my explanation in the previous message, and after your answer,
> I have the feeling it may sounds like I'm making up words needing
> persuasion. Probably I'm misunderstanding. Just in case, please allow
> me a clarification.
No, that was not my intent at all. It's a term I haven't encountered
before, but that doesn't mean you made it up :)
Thanks,
jon
next prev parent reply other threads:[~2025-12-23 21:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 21:46 [PATCH v2 1/1] docs: Update documentation to avoid mentioning of kernel.h Andy Shevchenko
2025-11-27 0:26 ` Randy Dunlap
2025-11-29 15:24 ` Andy Shevchenko
2025-11-29 15:54 ` Jonathan Corbet
2025-11-29 17:46 ` Andy Shevchenko
2025-11-27 17:34 ` Joe Perches
2025-11-27 18:19 ` Andy Shevchenko
2025-12-05 11:15 ` [PATCH] Doc:it_IT: Do not reference kernel.h anymore Andi Shyti
2025-12-15 0:30 ` Federico Vaga
2025-12-15 16:14 ` Andi Shyti
2025-12-17 22:48 ` Federico Vaga
2025-12-22 22:01 ` Jonathan Corbet
2025-12-23 21:22 ` Federico Vaga
2025-12-23 21:34 ` Jonathan Corbet [this message]
2025-12-05 15:25 ` [PATCH v2 1/1] docs: Update documentation to avoid mentioning of kernel.h Mathieu Poirier
2025-12-22 22:00 ` Jonathan Corbet
2025-12-28 18:02 ` Andy Shevchenko
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=87h5tgubkq.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@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