From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"David Gow" <davidgow@google.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kbuild@vger.kernel.org,
automated-testing@lists.yoctoproject.org,
workflows@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v2 1/2] scripts: add tool to run containerized builds
Date: Mon, 22 Dec 2025 11:12:10 -0500 [thread overview]
Message-ID: <20251222-aboriginal-guppy-of-charisma-49fe02@lemur> (raw)
In-Reply-To: <09b3bc78-6c55-4d8c-8d09-9f313454dee3@gtucker.io>
On Mon, Dec 22, 2025 at 10:11:25AM +0100, Guillaume Tucker wrote:
> Ah yes, good point. Except right now it's returning HTTP 403...
> Hopefully that's just a temporary technical glitch.
(it was)
-K
next prev parent reply other threads:[~2025-12-22 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 12:49 [PATCH v2 0/2] scripts: introduce " Guillaume Tucker
2025-12-18 12:49 ` [PATCH v2 1/2] scripts: add tool to run " Guillaume Tucker
2025-12-19 21:27 ` Nathan Chancellor
2025-12-21 20:09 ` Guillaume Tucker
2025-12-30 20:23 ` Nathan Chancellor
2025-12-21 20:19 ` Guillaume Tucker
2025-12-22 3:30 ` Miguel Ojeda
2025-12-22 9:11 ` Guillaume Tucker
2025-12-22 16:12 ` Konstantin Ryabitsev [this message]
2025-12-18 12:49 ` [PATCH v2 2/2] Documentation: dev-tools: add container.rst page Guillaume Tucker
2025-12-21 20:13 ` Guillaume Tucker
2025-12-30 20:16 ` Nathan Chancellor
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=20251222-aboriginal-guppy-of-charisma-49fe02@lemur \
--to=konstantin@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=automated-testing@lists.yoctoproject.org \
--cc=davidgow@google.com \
--cc=gtucker@gtucker.io \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.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