From: Julian Braha <julianbraha@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, ljs@kernel.org, arnd@arndb.de,
masahiroy@kernel.org, nathan@kernel.org, nsc@kernel.org,
ojeda@kernel.org, corbet@lwn.net, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] scripts: add kconfirm
Date: Tue, 28 Apr 2026 22:17:26 +0100 [thread overview]
Message-ID: <0751366c-2aa6-461d-87a3-84309f3c4735@gmail.com> (raw)
In-Reply-To: <2026042727-delicate-genre-21fa@gregkh>
On Mon, 27 Apr 2026, Greg KH <gregkh@linuxfoundation.org> wrote:
> You don't say what this fancy new tool actually does anywhere that I can
> see :(
Hi Greg, apologies, I wrote everything in the cover letter:
https://lore.kernel.org/all/20260427174429.779474-1-julianbraha@gmail.com/
and then I wasn't really sure what to write in the actual patch
messages...
I'll spend some more time looking through past RFCs and either separate
things out, or add some repetition.
> Did you mean to check this file in? That's not going to work well...
I've found some ways to significantly reduce the size of the
dependencies when vendored (also thanks to Arnd), details already shared
here:
https://lore.kernel.org/all/d72badf8-7d70-4caa-96a9-d77e00bbb536@gmail.com/
so then we can remove the internet connection for dependency download,
and the Cargo.lock file becomes unnecessary.
- Julian Braha
next prev parent reply other threads:[~2026-04-28 21:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:44 [RFC PATCH 0/2] scripts: add kconfirm Julian Braha
2026-04-27 17:44 ` [RFC PATCH 1/2] " Julian Braha
2026-04-27 20:48 ` Greg KH
2026-04-28 21:17 ` Julian Braha [this message]
2026-04-28 7:01 ` Jonathan Corbet
2026-04-28 18:31 ` Nathan Chancellor
2026-04-28 19:08 ` Jonathan Corbet
2026-04-27 17:44 ` [RFC PATCH 2/2] Documentation: dev-tools: " Julian Braha
2026-04-27 18:17 ` Miguel Ojeda
2026-04-27 19:33 ` Arnd Bergmann
2026-04-28 11:51 ` Miguel Ojeda
2026-04-28 12:58 ` Gary Guo
2026-04-28 18:45 ` Nathan Chancellor
2026-04-28 17:01 ` Julian Braha
2026-04-28 8:23 ` Jani Nikula
2026-04-28 18:06 ` Julian Braha
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=0751366c-2aa6-461d-87a3-84309f3c4735@gmail.com \
--to=julianbraha@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@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