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.
All right, I've got ollama working on my gaming rig now, so that I can get back to my summarization work without having to rely on big vendors. Thanks for pushing me in that direction, because it never felt quite right to be using a centralized service for this work. At least that large nvidia card does something other than help me deliver packages to Port Knot City. > The command: > - Takes a message ID and constructs a detailed prompt about email > relationships > - Calls a configured AI agent script to analyze and find related messages > - Downloads all related threads from lore.kernel.org > - Combines them into a single mbox file for easy review I'm going to take a look at it, but I want to use "b4 dig" to analyze commits and establish their provenance. I will then look at whether we can use LLMs to provide additional perks like summarization or highlights of important messages (those offering nacks, criticisms, warnings, etc). This seems like the "least wrong" way of using an LLM at this moment, especially with the legality of the code it produces still largely untested in courts. Thanks for submitting this to push me into this direction. I won't take this directly, but I'll rely on it to see how you get certain things done. Regards, -K
