From: Jonathan Corbet <corbet@lwn.net>
To: Doehyun Baek <doehyunbaek@gmail.com>
Cc: linux-doc@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
Federico Vaga <federico.vaga@vaga.pv.it>
Subject: Re: [PATCH] Docs/translations/it_IT: update current minimal requirements
Date: Thu, 25 Jun 2026 06:49:44 -0600 [thread overview]
Message-ID: <878q826azb.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAN-j9UqSuCWikosJzu+kcU=cOwnfRzYkr85hXS24AqSf=qwVwQ@mail.gmail.com>
Doehyun Baek <doehyunbaek@gmail.com> writes:
> Hi Jonathan,
>
> Gentle ping on this patch. Federico replied that it looks good to him.
>
> If nothing else is needed, could this be applied to docs-next?
We're in the merge window, which slows things down.
In this case, as well, the patch doesn't apply to docs-next. Please
send a version that does, and I'll apply it after the merge window
closes.
Thanks,
jon
prev parent reply other threads:[~2026-06-25 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 8:53 [PATCH] Docs/translations/it_IT: update current minimal requirements Doehyun Baek
2026-06-17 13:43 ` Federico Vaga
2026-06-25 6:47 ` Doehyun Baek
2026-06-25 12:49 ` Jonathan Corbet [this message]
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=878q826azb.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