From: Demi Marie Obenour <demiobenour@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Julian Braha <julianbraha@gmail.com>,
nathan@kernel.org, nsc@kernel.org, jani.nikula@linux.intel.com,
akpm@linux-foundation.org, gary@garyguo.net, ljs@kernel.org,
arnd@arndb.de, gregkh@linuxfoundation.org, masahiroy@kernel.org,
ojeda@kernel.org, corbet@lwn.net, qingfang.deng@linux.dev,
yann.prono@telecomnancy.net, ej@inai.de,
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 v3 1/3] scripts: add kconfirm
Date: Sun, 17 May 2026 05:32:52 -0400 [thread overview]
Message-ID: <18809682-aa16-4ab4-b615-cefa525c872f@gmail.com> (raw)
In-Reply-To: <CANiq72=9nxRgfFf1WzWgp=TP9or=Mi=wLyME9-f2M4hti+ZNcg@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 842 bytes --]
On 5/17/26 05:30, Miguel Ojeda wrote:
> On Sun, May 17, 2026 at 9:32 AM Demi Marie Obenour
> <demiobenour@gmail.com> wrote:
>>
>> Using a ton of vendored dependencies would make for unreviewable
>> patches.
>
> I am referring to `cargo vendor` here, not to copying in-tree -- we
> already discussed that in previous versions.
That's true. Some distros (Fedora, Debian) don't like that either,
but that's a bigger ecosystem-wide concern.
> Please note that I was arguing for avoiding actual vendoring in
> previous versions...
>
>> I'm the one who suggested using FFI here and for command-line parsing.
>> The command-line interface would also work.
>
> Yes, I suggested the CLI in v1, and then you mentioned the library in v2.
CLI would also work just as well.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-17 9:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 21:53 [RFC v3 0/3] add kconfirm Julian Braha
2026-05-16 21:53 ` [RFC PATCH v3 1/3] scripts: " Julian Braha
2026-05-17 6:10 ` Demi Marie Obenour
2026-05-17 9:58 ` Miguel Ojeda
2026-05-17 20:25 ` Demi Marie Obenour
2026-05-17 22:53 ` Miguel Ojeda
2026-05-17 6:28 ` Miguel Ojeda
2026-05-17 7:32 ` Demi Marie Obenour
2026-05-17 9:30 ` Miguel Ojeda
2026-05-17 9:32 ` Demi Marie Obenour [this message]
2026-05-17 9:48 ` Miguel Ojeda
2026-05-17 9:28 ` Nathan Chancellor
2026-05-16 21:53 ` [RFC PATCH v3 2/3] Documentation: " Julian Braha
2026-05-17 6:05 ` Miguel Ojeda
2026-05-17 9:40 ` Nathan Chancellor
2026-05-17 12:35 ` Miguel Ojeda
2026-05-16 21:53 ` [RFC PATCH v3 3/3] MAINTAINERS: create entry for kconfirm Julian Braha
2026-05-16 22:36 ` [RFC v3 0/3] add kconfirm Julian Braha
2026-05-17 6:14 ` Demi Marie Obenour
2026-05-17 23:21 ` 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=18809682-aa16-4ab4-b615-cefa525c872f@gmail.com \
--to=demiobenour@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=ej@inai.de \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=julianbraha@gmail.com \
--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=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=qingfang.deng@linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=yann.prono@telecomnancy.net \
/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