From: Daniel Borkmann <daniel@iogearbox.net>
To: konstantin@linuxfoundation.org
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: Tue, 1 Oct 2019 23:33:06 +0200 [thread overview]
Message-ID: <a01ead7c-94ce-12ef-a043-6fd492c6c431@iogearbox.net> (raw)
In-Reply-To: <20190930212410.GE14403@pure.paranoia.local>
On 9/30/19 11:24 PM, Konstantin Ryabitsev wrote:
> On Mon, Sep 23, 2019 at 02:52:01PM +0200, Daniel Borkmann wrote:
>>> Most (all) of the "kit" functionality should be separated from the UI
>>> and be available for scripting/automation/other UIs. Whether it's
>>> done as "libgit" or as "shell out" is discussable.
>> [...]
>> On that note, such a tool would also need to co-exist with the current
>> email based process for some (long?) time in order to allow a smooth
>> transition period. Last week I spent a few of nights hacking a small tool
>> which is regularly pulling the lore git trees I'm interested in and checking
>> out all [new] mails into maildir format so they can be read naturally by
>> UIs like mutt et al [0]. As an experiment, in case of bpf vger mailing list,
>> it extracts all current ~8k mails in under a second:
>
> 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.)
Thanks,
Daniel
[0] https://git.kernel.org/pub/scm/linux/kernel/git/dborkman/l2md.git/
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <daniel@iogearbox.net>
To: konstantin@linuxfoundation.org
Cc: Dmitry Vyukov <dvyukov@gmail.com>,
ksummit-discuss@lists.linuxfoundation.org, tytso@mit.edu,
robh@kernel.org, laurent.pinchart@ideasonboard.com,
rjw@rjwysocki.net, workflows@vger.kernel.org,
skhan@linuxfoundation.org, gregkh@linuxfoundation.org,
helgaas@kernel.org, jikos@kernel.org, jani.nikula@intel.com,
geert@linux-m68k.org, stefan@datenfreihafen.org,
sashal@kernel.org, hch@lst.de, Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Reflections on kernel development processes
Date: Tue, 1 Oct 2019 23:33:06 +0200 [thread overview]
Message-ID: <a01ead7c-94ce-12ef-a043-6fd492c6c431@iogearbox.net> (raw)
In-Reply-To: <20190930212410.GE14403@pure.paranoia.local>
On 9/30/19 11:24 PM, Konstantin Ryabitsev wrote:
> On Mon, Sep 23, 2019 at 02:52:01PM +0200, Daniel Borkmann wrote:
>>> Most (all) of the "kit" functionality should be separated from the UI
>>> and be available for scripting/automation/other UIs. Whether it's
>>> done as "libgit" or as "shell out" is discussable.
>> [...]
>> On that note, such a tool would also need to co-exist with the current
>> email based process for some (long?) time in order to allow a smooth
>> transition period. Last week I spent a few of nights hacking a small tool
>> which is regularly pulling the lore git trees I'm interested in and checking
>> out all [new] mails into maildir format so they can be read naturally by
>> UIs like mutt et al [0]. As an experiment, in case of bpf vger mailing list,
>> it extracts all current ~8k mails in under a second:
>
> 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.)
Thanks,
Daniel
[0] https://git.kernel.org/pub/scm/linux/kernel/git/dborkman/l2md.git/
next prev parent reply other threads:[~2019-10-01 21:33 UTC|newest]
Thread overview: 39+ 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
2019-09-22 12:02 ` Dmitry Vyukov
2019-09-23 12:52 ` Daniel Borkmann
2019-09-23 12:52 ` Daniel Borkmann
2019-09-23 14:08 ` Dmitry Vyukov via Ksummit-discuss
2019-09-23 14:08 ` Dmitry Vyukov
2019-09-23 14:57 ` Daniel Borkmann
2019-09-23 14:57 ` Daniel Borkmann
2019-09-30 21:24 ` Konstantin Ryabitsev
2019-09-30 21:24 ` Konstantin Ryabitsev
2019-10-01 21:33 ` Daniel Borkmann [this message]
2019-10-01 21:33 ` Daniel Borkmann
2019-10-02 15:04 ` Konstantin Ryabitsev
2019-10-02 15:04 ` Konstantin Ryabitsev
2019-09-30 20:24 ` Konstantin Ryabitsev
2019-10-08 6:46 ` Dmitry Vyukov
2019-10-08 16:51 ` Konstantin Ryabitsev
2019-10-11 2:16 ` Konstantin Ryabitsev
2019-10-11 2:30 ` Steven Rostedt
2019-10-11 8:30 ` Greg Kroah-Hartman
2019-10-11 8:59 ` Dmitry Vyukov
2019-10-11 9:33 ` Dmitry Vyukov
2019-10-11 9:40 ` Christian Brauner
2019-10-11 13:18 ` Steven Rostedt
2019-10-11 13:19 ` Christian Brauner
2019-10-11 13:30 ` Dmitry Vyukov
2019-10-11 13:40 ` Laurent Pinchart
2019-10-11 15:28 ` Jonathan Corbet
2019-10-14 7:42 ` Nicolas Belouin
2019-10-14 7:52 ` Daniel Vetter
2019-10-15 7:31 ` Dmitry Vyukov
2019-10-15 16:17 ` Konstantin Ryabitsev
2019-10-11 10:46 ` Dmitry Vyukov
2019-10-11 13:29 ` Laurent Pinchart
2019-10-11 13:51 ` Theodore Y. Ts'o
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=a01ead7c-94ce-12ef-a043-6fd492c6c431@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=dvyukov@gmail.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=konstantin@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.