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,
automated-testing@lists.yoctoproject.org
Subject: Re: [PATCH 2/2] Documentation: dev-tools: update container.rst with config file
Date: Fri, 28 Aug 2026 08:35:01 +0200 [thread overview]
Message-ID: <be36c78e-6aa3-4efc-92d8-12bef33d8aa0@gtucker.io> (raw)
In-Reply-To: <fa01a427-a73b-460b-9b11-d2e92cb8ea9a@gtucker.io>
On 24/08/2026 12:55 pm, Guillaume Tucker wrote:
> On 24/08/2026 12:05, Guillaume Tucker wrote:
>> +By default, the tool will look for configuration a file named
>> +``.container.toml`` in the current working directory. If not found, it will be
>
> Sorry, a small typo crept in:
>
> -By default, the tool will look for configuration a file named
> +By default, the tool will look for a configuration file named
I just sent a v2 with this fix.
Guillaume
next prev parent reply other threads:[~2026-08-28 6:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 10:05 [PATCH 1/2] scripts: add TOML config to container tool Guillaume Tucker
2026-08-24 10:05 ` [PATCH 2/2] Documentation: dev-tools: update container.rst with config file Guillaume Tucker
2026-08-24 10:55 ` Guillaume Tucker
2026-08-28 6:35 ` Guillaume Tucker [this message]
2026-08-28 6:39 ` [PATCH 1/2] scripts: add TOML config to container tool Guillaume Tucker
2026-08-28 16:29 ` Nicolas Schier
2026-08-28 17:25 ` Guillaume Tucker
2026-08-28 17:35 ` Miguel Ojeda
2026-08-29 8:56 ` Guillaume Tucker
2026-08-29 11:01 ` Miguel Ojeda
2026-08-29 9:02 ` Guillaume Tucker
2026-08-29 10:57 ` Miguel Ojeda
2026-09-02 10:26 ` 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=be36c78e-6aa3-4efc-92d8-12bef33d8aa0@gtucker.io \
--to=gtucker@gtucker.io \
--cc=automated-testing@lists.yoctoproject.org \
--cc=corbet@lwn.net \
--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