From: Jonathan Corbet <corbet@lwn.net>
To: Coiby Xu <coiby.xu@gmail.com>, linux-doc@vger.kernel.org
Cc: Guillaume Tucker <gtucker@gtucker.io>,
Shuah Khan <skhan@linuxfoundation.org>,
"open list:DOCUMENTATION PROCESS" <workflows@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: dev-tools: scripts/container prefers Podman
Date: Tue, 30 Jun 2026 13:52:36 -0600 [thread overview]
Message-ID: <87jyrfrekb.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260624013850.1853171-1-coiby.xu@gmail.com>
Coiby Xu <coiby.xu@gmail.com> writes:
> Obviously scripts/container prefers Podman over Docker. Putting podman
> before docker also makes it consistent with following parts of the doc
> and the help text of the tool.
>
> Signed-off-by: Coiby Xu <coiby.xu@gmail.com>
> ---
> Documentation/dev-tools/container.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2026-06-30 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 1:38 [PATCH] Documentation: dev-tools: scripts/container prefers Podman Coiby Xu
2026-06-24 21:02 ` Guillaume Tucker
2026-06-25 10:05 ` Coiby Xu
2026-06-30 19:52 ` 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=87jyrfrekb.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=coiby.xu@gmail.com \
--cc=gtucker@gtucker.io \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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