Re: lore+lei: getting started

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Fri, Nov 5, 2021 at 12:07 PM Konstantin Ryabitsev
<konstantin@xxxxxxxxxxxxxxxxxxx> wrote:
> Hello, all:
> I am going to post a series of articles about public inbox's new lei tool
> (stands for "local email interface", but is clearly a "lorelei" joke :)). In
> addition to being available here on the workflows list, they will also be
> posted on my blog.
> ## What's the problem?
> One of kernel developers' perennial complaints is that they just get Too Much
> Damn Email. Nobody in their right mind subscribes to "the LKML"
> (linux-kernel@xxxxxxxxxxxxxxx) because it acts as a dumping ground for all
> email and the resulting firehose of patches and rants is completely impossible
> for a sane human being to follow.
> For this reason, actual Linux development tends to happen on separate mailing
> lists dedicated to each particular subsystem. In turn, this has several
> negative side-effects:
> 1. Developers working across multiple subsystems end up needing to subscribe
>    to many different mailing lists in order to stay aware of what is happening
>    in each area of the kernel.
> 2. Contributors submitting patches find it increasingly difficult to know
>    where to send their work, especially if their patches touch many different
>    subsystems.
> The `` script is an attempt to solve the problem #2, and will
> look at the diff contents in order to suggest the list of recipients for each
> submitted patch. However, the submitter needs to be both aware of this script
> and know how to properly configure it in order to correctly use it with
> git-send-email.
> Further complicating the matter is the fact that `` relies on
> the entries in the `MAINTAINERS` file. Any edits to that file must go through
> the regular patch submission and review process and it may take days or weeks
> before the updates find their way to individual contributors.
> Wouldn't it be nice if contributors could just send their patches to one
> place, and developers could just filter out the stuff that is relevant to
> their subsystem and ignore the rest?
> ## lore meets lei
> Public-inbox started out as a distributed mailing list archival framework with
> powerful search capabilities. We were happy to adopt it for our needs when we
> needed a proper home for kernel mailing list archives -- thus,
> came online.
> Even though it started out as merely a list archival service, it quickly
> became obvious that lore could be used for a lot more. Many developers ended
> up using its search features to quickly locate emails of interest, which in
> turn raised a simple question -- what if there was a way to "save a search"
> and have it deliver all new incoming mail matching certain parameters straight
> to the developers' inbox?
> You can now do this with lei.
> ## lore's search syntax
> Public-inbox uses Xapian behind the scenes, which allows to narrowly tailor
> the keyword database to very specific needs.
> For example, did you know that you can search for patches that
> touch specific files? Here's every patch that touched the MAINTAINERS file:
> *
> How about every patch that modifies a function that starts with `floppy_`:
> **
> Say you're the floppy driver maintainer and wanted to find all mail that
> touches `drivers/block/floppy.c` and modifies any function that starts with
> `floppy_` or has "floppy" in the subject and maybe any other mail that
> mentions "floppy" and has the words "bug" or "regression"? And maybe limit the
> results to just the past month.
> Here's the query:
>     (dfn:drivers/block/floppy.c OR dfhh:floppy_* OR s:floppy
>      OR ((nq:bug OR nq:regression) AND nq:floppy))
>     AND rt:1.month.ago..
> And here are the results:
> **+OR+dfn%3Adrivers%2Fblock%2Ffloppy.c+OR+s%3Afloppy+OR+%28%28nq%3Abug+OR+nq%3Aregression%29+AND+nq%3Afloppy%29%29+AND+rt%3A1.month.ago..
> Now, how about getting that straight into your mailbox, so you don't have to
> subscribe to the (very busy) linux-block list, if you are the floppy
> maintainer?
> ## Installing lei
> Lei is very new and probably isn't yet available as part of your distribution,
> but I hope that it will change quickly once everyone realizes how awesome it
> is.
> I'm working on packaging lei for Fedora, so depending on when you're reading
> this, try `dnf install lei` -- maybe it's already there. If it's not in Fedora
> proper yet, you can get it from my copr:
>     dnf copr enable icon/b4
>     dnf install lei
> If you're not a Fedora user, just consult the INSTALL file:
> *
> ## Maildir or IMAP?
> Lei can deliver search results either into a local maildir, or to a remote
> IMAP folder (or both). We'll do local maildir first and look at IMAP in a
> future follow-up, as it requires some preparatory work.
> ## Getting going with lei-q
> Let's take the exact query we used for the floppy drive above, and get lei to
> deliver entire matching threads into a local maildir folder that we can read
> with mutt:
>     lei q -I -o ~/Mail/floppy \
>       --threads --dedupe=mid \
>       '(dfn:drivers/block/floppy.c OR dfhh:floppy_* OR s:floppy \
>       OR ((nq:bug OR nq:regression) AND nq:floppy)) \
>       AND rt:1.month.ago..'

I tried a similar one which I had working as a bookmark:

$ lei q -I -o ~/Mail/my-patches
--threads --dedupe=mid '(dfn:drivers OR dfn:arch OR dfn:Documentation
OR dfn:include OR dfn:scripts) AND f:robh@xxxxxxxxxx'
# /home/rob/.local/share/lei/store 0/0
# /usr/bin/curl -Sf -s -d ''
# 0 written to /home/rob/Mail/my-patches/ (0 matches)

It seems there is some problem in quoting. Notice the '%22' that's
inserted in the url.

Also, the above query is a bit of a work-around as what I really want
is just all patches from me. I haven't been able to get something to
work. I've tried things like 'dfn:*' or 'dfn:/' or 'dfn:b/'.


[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux