From: Nathan Chancellor <nathan@kernel.org>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Nicolas Schier" <nsc@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,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Onur Özkan" <work@onurozkan.dev>
Subject: Re: [PATCH 1/2] scripts: add TOML config to container tool
Date: Thu, 3 Sep 2026 13:27:00 -0700 [thread overview]
Message-ID: <20260903202700.GA3790602@ax162> (raw)
In-Reply-To: <ed43b869-6fd4-4b00-8fd2-e9dd9aaf3349@gtucker.io>
On Wed, Sep 02, 2026 at 12:26:29PM +0200, Guillaume Tucker wrote:
> So to recap, here's what I would suggest:
>
> * keep Python 3.10 for this series, continue discussion about minimum
> and optional version numbers tree-wide in other threads
>
> * drop registry config file option in v4 then add it in a follow-up
> series along with image name validation and parsing using regex
>
> * leave TypeError exceptions as-is in this series, improve user
> experience and error handling altogether in another follow-up
Sure, I think this sounds fine. I tend to ignore existing issue comments
from Sashiko when it comes to accepting a series, I would always prefer
them to be handled in a separate series.
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-09-03 20:27 UTC|newest]
Thread overview: 16+ 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
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-09-04 16:29 ` Nicolas Schier
2026-08-29 9:02 ` Guillaume Tucker
2026-08-29 10:57 ` Miguel Ojeda
2026-09-02 10:26 ` Guillaume Tucker
2026-09-03 20:27 ` Nathan Chancellor [this message]
2026-09-07 11:28 ` 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=20260903202700.GA3790602@ax162 \
--to=nathan@kernel.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=corbet@lwn.net \
--cc=gtucker@gtucker.io \
--cc=kernelci@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.