Re: RFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org

Pratyush Yadav
2023-11-07T13:23:42Z

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