From: Willy Tarreau <w@1wt.eu>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Mark Brown <broonie@kernel.org>,
users@kernel.org, tools@kernel.org, workflows@vger.kernel.org
Subject: Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
Date: Wed, 28 Feb 2024 16:29:53 +0100 [thread overview]
Message-ID: <Zd9RcdLAiEdB/7w2@1wt.eu> (raw)
In-Reply-To: <20240228-ethereal-swine-of-renovation-b1d7c7@meerkat>
On Wed, Feb 28, 2024 at 10:22:41AM -0500, Konstantin Ryabitsev wrote:
> On Wed, Feb 28, 2024 at 02:03:31PM +0000, Mark Brown wrote:
> > > I figured a number of shortcomings about this: I suspect that those
> > > most interested in such output are either, a bit like me, not much
> > > active on kernel development, or focus on a specific area and mostly
> > > want to stay aware of ongoing changes in other areas they're really
> > > not familiar with.
> >
> > I can imagine using this sort of thing for the case where I get to my
> > inbox in the morning and there's some enormous thread appeared overnight
> > with people arguing and I'm trying to get a handle on what the various
> > subthreads are all about. The demo didn't cover exactly that case but
> > it looked like it might be able to give some sort of useful steer.
>
> Another use for this that I could think is a way to summarize digests.
> Currently, if you choose a digest subscription, you will receive a single
> email with message subjects and all the new messages as individual
> attachments. It would be interesting to see if we can send out a "here's
> what's new" summary with links to threads instead.
Indeed!
> The challenge would be to do it in a way that doesn't bankrupt LFIT in the
> process. :)
That's exactly why it would make sense to invest in one large machine
and let it operate locally while "only" paying the power bill.
Willy
next prev parent reply other threads:[~2024-02-28 15:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 22:32 Konstantin Ryabitsev
2024-02-27 23:35 ` Junio C Hamano
2024-02-28 0:43 ` Linus Torvalds
2024-02-28 20:46 ` Shuah Khan
2024-02-29 0:33 ` James Bottomley
2024-02-28 5:00 ` Willy Tarreau
2024-02-28 14:03 ` Mark Brown
2024-02-28 14:39 ` Willy Tarreau
2024-02-28 15:22 ` Konstantin Ryabitsev
2024-02-28 15:29 ` Willy Tarreau [this message]
2024-02-28 17:52 ` Konstantin Ryabitsev
2024-02-28 17:58 ` Willy Tarreau
2024-02-28 19:16 ` Konstantin Ryabitsev
2024-02-28 15:04 ` Hannes Reinecke
2024-02-28 15:15 ` Willy Tarreau
2024-02-28 17:43 ` Jonathan Corbet
2024-02-28 18:52 ` Alex Elder
2024-02-28 18:55 ` Bart Van Assche
2024-02-29 7:18 ` Hannes Reinecke
2024-02-29 8:37 ` Theodore Ts'o
2024-03-01 1:13 ` Bart Van Assche
2024-02-29 9:30 ` James Bottomley
2024-02-28 19:32 ` Luis Chamberlain
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=Zd9RcdLAiEdB/7w2@1wt.eu \
--to=w@1wt.eu \
--cc=broonie@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
--cc=users@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox