From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Walleij <linusw@kernel.org>
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
tools@kernel.org, users@kernel.org
Subject: Re: korgalore v0.2 released with JMAP, IMAP, Maildir support
Date: Mon, 22 Dec 2025 10:50:39 -0500 [thread overview]
Message-ID: <20251222-speedy-tuscan-salmon-4bfbb8@lemur> (raw)
In-Reply-To: <CAD++jLmwVSGwBZgSrbhcJ+w4BHWrgK57sBmMGR=ELRsHM+MzHQ@mail.gmail.com>
On Sat, Dec 20, 2025 at 09:56:31PM +0100, Linus Walleij wrote:
> Some examples on how to use it to get "your personal developer
> feed" using lei with korgalore would be deeply appreciated.
This is the next step -- this tool is a stepping stone towards the "maintainer
container" I talked about in my tooling update. I'm hoping to have a small web
frontend (accessed via localhost) that can manage most of the korgalore
configuration, which would also assist with putting together lei queries.
It could also help automatically convert F: and X: patterns from the
MAINTAINERS file into a lei query, so that someone would just have to pick
their subsystem to have the (mostly) right lei query set up for them.
> In my old gmail setup I have a "!TO-ME" folde which labels all
> messages from all subscribed lists where I am listed on To: or
> Cc: and put into that mailbox, I assume I can achieve the same
> with lei I just need to figure out how.
You want:
tc:linusw@kernel.org
The following query should do the trick:
lei q -O https://lore.kernel.org/all/ \
-o v2:/home/[username]/.local/share/lei/to-me \
--dedupe=mid \
'tc:linusw@kernel.org AND d:1.month.ago..'
Then you can add a korgalore lei feed:
[deliveries.to-me]
feed = 'lei:/home/user/.local/share/lei/to-me'
target = 'work'
labels = ['!TO-ME', 'UNREAD', 'STARRED']
-K
next prev parent reply other threads:[~2025-12-22 15:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 15:21 korgalore v0.2 released with JMAP, IMAP, Maildir support Konstantin Ryabitsev
2025-12-17 17:50 ` Jason A. Donenfeld
2025-12-17 18:14 ` Konstantin Ryabitsev
2025-12-18 0:24 ` Linus Walleij
2025-12-18 1:57 ` Konstantin Ryabitsev
2025-12-18 2:42 ` Konstantin Ryabitsev
2025-12-18 18:51 ` Sudeep Holla
2025-12-18 20:47 ` Konstantin Ryabitsev
2025-12-18 22:41 ` Linus Walleij
2025-12-19 0:38 ` Konstantin Ryabitsev
2025-12-20 20:56 ` Linus Walleij
2025-12-22 15:50 ` Konstantin Ryabitsev [this message]
2025-12-22 22:33 ` Linus Walleij
2026-01-09 23:31 ` Linus Walleij
2026-01-11 20:15 ` Konstantin Ryabitsev
2026-01-12 19:52 ` Linus Walleij
2026-01-12 19:55 ` Bugspray Bot
2026-01-12 20:49 ` Konstantin Ryabitsev
2026-01-13 13:03 ` Sudeep Holla
2026-01-13 15:52 ` Konstantin Ryabitsev
2026-01-14 10:05 ` Sudeep Holla
2026-01-13 17:29 ` Rob Herring
2026-01-13 17:41 ` Konstantin Ryabitsev
2026-01-15 17:27 ` Sudeep Holla
2025-12-22 14:02 ` Linus Walleij
2025-12-22 15:11 ` Linus Walleij
2025-12-22 15:23 ` Konstantin Ryabitsev
2025-12-22 22:28 ` Linus Walleij
2025-12-19 18:54 ` Sudeep Holla
2025-12-19 19:20 ` Konstantin Ryabitsev
2025-12-18 13:40 ` Rob Herring
2025-12-18 13:51 ` Rob Herring
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=20251222-speedy-tuscan-salmon-4bfbb8@lemur \
--to=konstantin@linuxfoundation.org \
--cc=linusw@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=tools@kernel.org \
--cc=users@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