ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	 Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	 Paolo Bonzini <pbonzini@redhat.com>, Pavel Machek <pavel@ucw.cz>,
	 Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	 users@linux.kernel.org, ksummit@lists.linux.dev
Subject: Re: RFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org
Date: Tue, 07 Nov 2023 14:23:39 +0100	[thread overview]
Message-ID: <mafs0ttpxg0is.fsf_-_@kernel.org> (raw)
In-Reply-To: <b36d7b18-2092-1848-e22a-7e34588db0f5@inria.fr> (Julia Lawall's message of "Tue, 7 Nov 2023 07:47:23 -0500 (EST)")

On Tue, Nov 07 2023, Julia Lawall wrote:

> At various times, I have wanted to see the discussion that led up to a
> commit, and LKML was the obvious place to go for that.  What will be the
> approach to take in the future?

I use lei with lore.kernel.org/all for that. For example, say I want to
see the discussion behind b6094ac83dd4 ("mtd: spi-nor: core: Introduce
spi_nor_set_4byte_addr_mode()"). I run the below query (on lore or on
lei, whichever suits your workflow) [0]:

   s:mtd: spi-nor: core: Introduce spi_nor_set_4byte_addr_mode() 

I then get the emails associated with the patch. This also works for
patches that arrived before I subscribed to any of the mailing lists. So
I find this method to be more powerful and complete than subscribing to
mailing lists.

[0] I have written some bits of code to integrate lei with gnus which
makes it easy for me to quickly open and read email threads. In the
background, it essentially runs:

    lei q --no-save -O https://lore.kernel.org/all/ -o mboxrd:temp.mbox -t "s:mtd: spi-nor: core: Introduce spi_nor_set_4byte_addr_mode()"

which creates an mbox file with the results of the query. "-t" tells it
to fetch the whole thread of any email that matches this query. I then
create a gnus group from the mbox and read the emails. See the lei q man
page for more details: https://public-inbox.org/lei-q.html

Lei can do much more but right now this simple workflow works pretty
good for me.

-- 
Regards,
Pratyush Yadav

  parent reply	other threads:[~2023-11-07 13:23 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 15:33 Konstantin Ryabitsev
2023-11-06 15:43 ` Joe Perches
2023-11-06 15:52 ` Borislav Petkov
2023-11-06 16:05 ` [workflows]RFC: " Steven Rostedt
2023-11-06 16:29   ` Miquel Raynal
2023-11-06 17:45     ` Konstantin Ryabitsev
2023-11-08 16:19   ` Joe Perches
2023-11-08 16:44     ` Mark Brown
2023-11-08 18:16       ` Joe Perches
2023-11-08 19:04         ` Steven Rostedt
2023-11-08 19:14           ` Joe Perches
2023-11-08 19:34             ` Steven Rostedt
2023-11-08 20:07               ` [workflows]Re: " Steven Rostedt
2023-11-08 20:14                 ` Joe Perches
2023-11-08 20:36                   ` Joe Perches
2023-11-08 20:49                     ` Joe Perches
2023-11-08 20:56                       ` Steven Rostedt
2023-11-08 21:04                         ` Konstantin Ryabitsev
2023-11-08 21:11                           ` Steven Rostedt
2023-11-08 20:41                 ` Joe Perches
2023-11-09 11:21               ` Mark Brown
2023-11-09 11:29                 ` Laurent Pinchart
2023-11-09  8:32           ` Dan Carpenter
2023-11-09  9:27             ` Laurent Pinchart
2023-11-09 17:14               ` Alex Elder
2023-11-09 17:25                 ` Konstantin Ryabitsev
2023-11-09 19:11                   ` Joe Perches
2023-11-09 19:38                     ` Konstantin Ryabitsev
2023-11-09 23:16                       ` Jason Gunthorpe
2023-11-10  0:56                         ` Linus Torvalds
2023-11-10 17:04                           ` Jakub Kicinski
2023-11-10 17:24                             ` Konstantin Ryabitsev
2023-11-10 17:55                               ` Jakub Kicinski
2023-11-10 17:24                             ` Rob Herring
2023-11-10 18:04                               ` Jakub Kicinski
2023-11-09 15:51             ` Steven Rostedt
2023-11-09 16:08               ` Laurent Pinchart
2023-11-09 16:16                 ` Steven Rostedt
2023-11-06 16:11 ` RFC: " Eric W. Biederman
2023-11-06 17:05   ` Christoph Hellwig
2023-11-06 17:41     ` Konstantin Ryabitsev
2023-11-09  3:55       ` Ian Kelling
2023-11-11 16:57       ` Theodore Ts'o
2023-11-07  4:04     ` Willy Tarreau
2023-11-06 17:21   ` Eric Wong
2023-11-06 17:56     ` Eric W. Biederman
2023-11-09 14:24   ` Naveen N Rao
2023-11-06 17:23 ` Richard Weinberger
2023-11-06 20:52   ` Randy Dunlap
2023-11-06 21:37 ` Jakub Kicinski
2023-11-06 22:52 ` Pavel Machek
2023-11-07  9:18   ` Paolo Bonzini
2023-11-07 10:15     ` Laurent Pinchart
2023-11-07 10:42       ` Greg KH
2023-11-07 12:14       ` Pratyush Yadav
2023-11-07 12:47         ` Julia Lawall
2023-11-07 13:18           ` Dan Carpenter
2023-11-07 13:23           ` Pratyush Yadav [this message]
2023-11-07 16:35           ` Konstantin Ryabitsev
2023-11-07 16:43             ` Paolo Bonzini
2023-11-07 16:51               ` Konstantin Ryabitsev
2023-11-10 10:01                 ` Paolo Bonzini
2023-11-07 10:47     ` Mark Brown
2023-11-07 13:24 ` Dan Carpenter
2023-11-08 20:04 ` Bird, Tim
2023-11-08 21:03   ` Luck, Tony
2023-11-08 21:04   ` James Bottomley
2023-11-08 21:18     ` Johannes Berg
2023-11-08 21:30     ` Rob Herring
2023-11-21 14:53 ` Joe Perches
2023-11-21 18:08   ` Greg KH

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=mafs0ttpxg0is.fsf_-_@kernel.org \
    --to=pratyush@kernel.org \
    --cc=julia.lawall@inria.fr \
    --cc=konstantin@linuxfoundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=pavel@ucw.cz \
    --cc=pbonzini@redhat.com \
    --cc=users@linux.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