From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: robh@kernel.org, ksummit-discuss@lists.linuxfoundation.org,
gregkh@linuxfoundation.org, Dmitry Vyukov <dvyukov@gmail.com>,
helgaas@kernel.org, workflows@vger.kernel.org,
Dmitry Vyukov <dvyukov@google.com>,
hch@lst.de, stefan@datenfreihafen.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Reflections on kernel development processes
Date: Wed, 2 Oct 2019 11:04:58 -0400 [thread overview]
Message-ID: <20191002150458.GA5611@pure.paranoia.local> (raw)
In-Reply-To: <a01ead7c-94ce-12ef-a043-6fd492c6c431@iogearbox.net>
On Tue, Oct 01, 2019 at 11:33:06PM +0200, Daniel Borkmann wrote:
> > Thanks for working on this -- I've started on a similar tool in the
> > past, but got distracted and never completed it. In my implementation,
> > it was piping messages to procmail, which allowed writing complex rules
> > for folders/pre-processing, etc. May I suggest that your tool also
> > offers a stdout that can be piped to procmail?
>
> I have a rough version working now. ;-) Just pushed to [0]. Let me know if that
> does the trick on your side, I've added example configs for procmail to the repo
> as well for getting started. Did a quick run for l2md -> procmail -> mutt and
> seems fine as far as I can tell. (Patches always welcome of course.)
Nice, thanks! Until we have a better tool for holistic patch/series
management backed by public-inbox, this should allow folks to pre-filter
their messages.
Best,
-K
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
prev parent reply other threads:[~2019-10-02 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:08 [Ksummit-discuss] [MAINTAINERS SUMMIT] Reflections on kernel development processes Theodore Y. Ts'o
2019-09-12 10:56 ` [Ksummit-discuss] Video of Dmitry's Kernel Summit talk (Was: Reflections on kernel development processes) Theodore Y. Ts'o
2019-09-12 12:06 ` [Ksummit-discuss] [MAINTAINERS SUMMIT] Reflections on kernel development processes Konstantin Ryabitsev
2019-09-13 16:22 ` Rob Herring
2019-09-13 16:34 ` Laurent Pinchart
[not found] ` <d6e8f49e93ece6f208e806ece2aa85b4971f3d17.1569152718.git.dvyukov@google.com>
2019-09-23 12:52 ` Daniel Borkmann
2019-09-23 14:08 ` Dmitry Vyukov via Ksummit-discuss
2019-09-23 14:57 ` Daniel Borkmann
2019-09-30 21:24 ` Konstantin Ryabitsev
2019-10-01 21:33 ` Daniel Borkmann
2019-10-02 15:04 ` Konstantin Ryabitsev [this message]
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=20191002150458.GA5611@pure.paranoia.local \
--to=konstantin@linuxfoundation.org \
--cc=daniel@iogearbox.net \
--cc=dvyukov@gmail.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=robh@kernel.org \
--cc=stefan@datenfreihafen.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).