From: Guillaume Tucker <gtucker@gtucker.io>
To: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: "Onur Özkan" <work@onurozkan.dev>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
linux-doc@vger.kernel.org, workflows@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
kernelci@lists.linux.dev,
automated-testing@lists.yoctoproject.org
Subject: Re: [PATCH v3 2/3] Documentation: dev-tools: update container.rst with config file
Date: Wed, 2 Sep 2026 11:37:32 +0200 [thread overview]
Message-ID: <f90aa8e8-abc4-477f-ab52-839e42eadf70@gtucker.io> (raw)
In-Reply-To: <adc9eeb418f026ba2b18c4b2aa1e52443bf6f210.1788340031.git.gtucker@gtucker.io>
On 02/09/2026 11:07, Guillaume Tucker wrote:
> ``-r, --runtime RUNTIME``
>
> Container runtime name. Supported runtimes: ``docker``, ``podman``.
> @@ -53,8 +63,8 @@ Available options:
>
> User id to use inside the container.
>
> - If the ``-g`` option is not specified, the user id will also be used for
> - the group id.
> + If the ``-g`` option is not specified and no group id is defined in the
> + configuration file, the user id will also be set as the group id.
This chunk didn't apply cleanly on top of v7.2 so I've resent the
series after a rebase on v7.3-rc1. The rebase was trivial though.
Guillaume
next prev parent reply other threads:[~2026-09-02 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 9:07 [PATCH v3 1/3] scripts: add TOML config to container tool Guillaume Tucker
2026-09-02 9:07 ` [PATCH v3 2/3] Documentation: dev-tools: update container.rst with config file Guillaume Tucker
2026-09-02 9:37 ` Guillaume Tucker [this message]
2026-09-02 9:07 ` [PATCH v3 3/3] Documentation: dev-tools: refer to user ID rather than id Guillaume Tucker
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=f90aa8e8-abc4-477f-ab52-839e42eadf70@gtucker.io \
--to=gtucker@gtucker.io \
--cc=automated-testing@lists.yoctoproject.org \
--cc=corbet@lwn.net \
--cc=kernelci@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=work@onurozkan.dev \
--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