All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	konstantin@linuxfoundation.org, csander@purestorage.com,
	io-uring@vger.kernel.org, torvalds@linux-foundation.org,
	workflows@vger.kernel.org
Subject: Re: [RFC] b4 dig: Add AI-powered email relationship discovery command
Date: Tue, 9 Sep 2025 14:54:53 -0400	[thread overview]
Message-ID: <aMB3_VgB4mwp-bzP@laps> (raw)
In-Reply-To: <72dd17ad-5467-49d3-9f40-054b1bf875d5@kernel.dk>

On Tue, Sep 09, 2025 at 11:26:19AM -0600, Jens Axboe wrote:
>On 9/9/25 11:22 AM, Laurent Pinchart wrote:
>> On Tue, Sep 09, 2025 at 12:32:14PM -0400, Sasha Levin wrote:
>>> Add a new 'b4 dig' subcommand that uses AI agents to discover related
>>> emails for a given message ID. This helps developers find all relevant
>>> context around patches including previous versions, bug reports, reviews,
>>> and related discussions.
>>
>> That really sounds like "if all you have is a hammer, everything looks
>> like a nail". The community has been working for multiple years to
>> improve discovery of relationships between patches and commits, with
>> great tools such are lore, lei and b4, and usage of commit IDs, patch
>> IDs and message IDs to link everything together. Those provide exact
>> results in a deterministic way, and consume a fraction of power of what
>> this patch would do. It would be very sad if this would be the direction
>> we decide to take.
>
>Fully agree, this kind of lazy "oh just waste billions of cycles and
>punt to some AI" bs is just kind of giving up on proper infrastructure
>to support maintainers and developers.

This feels like a false choice: why force a pick between b4-dig-like tooling
and improving our infra? They can work together. As tagging and workflows
improve, those gains will flow into the tools anyway.

It's like saying we should skip -rc releases because they mean we've given up
on bug free code.

Perfect is the enemy of the good. You're arguing against a tool that works now,
just because it's not ideal, and to chase perfection instead. I'd rather be
"lazy" and skip the endless lore hunts.

-- 
Thanks,
Sasha

  reply	other threads:[~2025-09-09 18:54 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 11:18 [GIT PULL] io_uring fix for 6.17-rc5 Jens Axboe
2025-09-05 17:24 ` Linus Torvalds
2025-09-05 17:45   ` Konstantin Ryabitsev
2025-09-05 18:06     ` Linus Torvalds
2025-09-05 19:33       ` Link trailers revisited (was Re: [GIT PULL] io_uring fix for 6.17-rc5) Konstantin Ryabitsev
2025-09-05 20:09         ` Linus Torvalds
2025-09-05 20:47         ` Sasha Levin
2025-09-06 11:27         ` Greg KH
2025-09-06 11:27           ` Greg KH
2025-09-06 11:30             ` Greg KH
2025-09-06 13:51           ` Konstantin Ryabitsev
2025-09-06 15:31             ` Linus Torvalds
2025-09-06 18:50               ` Konstantin Ryabitsev
2025-09-06 19:19                 ` Linus Torvalds
2025-09-08  9:11                   ` Jani Nikula
2025-09-08 11:59                 ` Mark Brown
2025-09-08 20:11         ` dan.j.williams
2025-09-09 11:29           ` Mark Brown
2025-09-09 13:17           ` Rafael J. Wysocki
2025-09-09 14:18             ` Jakub Kicinski
2025-09-09 14:35               ` Jens Axboe
2025-09-09 14:42                 ` Konstantin Ryabitsev
2025-09-09 14:48                   ` Vlastimil Babka
2025-09-09 14:50                     ` Jens Axboe
2025-09-09 15:30                       ` Rafael J. Wysocki
2025-09-09 16:40                       ` Linus Torvalds
2025-09-09 17:08                         ` Mark Brown
2025-09-09 17:50                           ` Linus Torvalds
2025-09-09 17:58                             ` Linus Torvalds
2025-09-09 18:31                               ` Konstantin Ryabitsev
2025-09-09 19:36                                 ` dan.j.williams
2025-09-10  1:12                                 ` dan.j.williams
2025-09-10 12:19                                   ` Mark Brown
2025-09-09 17:25                         ` dan.j.williams
2025-09-09 17:56                           ` Alexei Starovoitov
2025-09-09 18:01                             ` Linus Torvalds
2025-09-09 18:13                               ` Alexei Starovoitov
2025-09-09 18:06                         ` Vlastimil Babka
2025-09-09 18:14                           ` Linus Torvalds
2025-09-09 18:22                             ` Vlastimil Babka
2025-09-09 21:05                               ` Mark Brown
2025-09-10  1:33                                 ` Konstantin Ryabitsev
2025-09-09 14:44                 ` Greg KH
2025-09-09 15:14                 ` Danilo Krummrich
2025-09-09 16:32         ` [RFC] b4 dig: Add AI-powered email relationship discovery command Sasha Levin
2025-09-09 17:22           ` Laurent Pinchart
2025-09-09 17:26             ` Jens Axboe
2025-09-09 18:54               ` Sasha Levin [this message]
2025-09-10 10:13                 ` Laurent Pinchart
2025-09-10 10:55                   ` Sasha Levin
2025-09-10 11:29                     ` Laurent Pinchart
2025-09-10 13:38             ` Konstantin Ryabitsev
2025-09-10 14:03               ` Andrew Dona-Couch
2025-09-11 14:48           ` Nicolas Frattaroli
2025-09-11 15:05             ` Sasha Levin
2025-09-11 19:13               ` Nicolas Frattaroli
2025-09-11 19:57                 ` Sasha Levin
2025-09-15 11:26                   ` Mark Brown
2025-09-15 11:48                     ` Sasha Levin
2025-09-15 12:03                       ` Mark Brown
2025-09-11 23:24           ` Konstantin Ryabitsev
2025-09-07 22:04     ` [GIT PULL] io_uring fix for 6.17-rc5 Jonathan Corbet
2025-09-05 19:04   ` Jens Axboe
2025-09-05 19:07     ` Jens Axboe
2025-09-05 19:13     ` Caleb Sander Mateos
2025-09-05 19:16       ` Jens Axboe
2025-09-05 19:15     ` Linus Torvalds
2025-09-05 19:23       ` Jens Axboe
2025-09-05 19:21     ` Linus Torvalds
2025-09-05 19:30       ` Jens Axboe
2025-09-05 20:54         ` Linus Torvalds
2025-09-06  0:01           ` Jens Axboe
2025-09-07 18:47             ` Jonathan Corbet
2025-09-08 22:15             ` Alexei Starovoitov

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=aMB3_VgB4mwp-bzP@laps \
    --to=sashal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=io-uring@vger.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=torvalds@linux-foundation.org \
    --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.