Re: Structured feeds

From: Stephen Finucane <stephen@that.guru>
To: Johannes Berg <johannes@sipsolutions.net>,
	Daniel Axtens <dja@axtens.net>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	patchwork@lists.ozlabs.org
Cc: workflows@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>,
	Brendan Higgins <brendanhiggins@google.com>,
	Han-Wen Nienhuys <hanwen@google.com>,
	automated-testing@yoctoproject.org,
	Dmitry Vyukov <dvyukov@google.com>
Subject: Re: Structured feeds
Date: Sat, 30 Nov 2019 18:36:36 +0000	[thread overview]
Message-ID: <30037ebd93d2949354582f472be98524d9d52ada.camel@that.guru> (raw)
In-Reply-To: <ac18c57edf7581b874399d6a4f6c1fb20c3a6543.camel@sipsolutions.net>

On Sat, 2019-11-30 at 19:16 +0100, Johannes Berg wrote:
> On Sat, 2019-11-30 at 18:04 +0000, Stephen Finucane wrote:
> 
> > > Somebody (Daniel Borkmann?) posted a (very fast) public-inbox git to
> > > maildir converter, with procmail support. I assume that would actually
> > > satisfy this step already, since you can just substitute the patchwork
> > > parser for procmail.
> > 
> > What do you mean "substitute the patchwork parser for procmail"? From
> > reading this thread, I got the impression that we'd be changing what
> > feeds things into the 'parsemail' management command, right?
> 
> Yes, that's exactly what I meant. I was looking at it from Daniel's
> tool's POV, so instead of calling procmail it can call patchwork.
> 
> johannes

Ah, then that I have no issues with :) I've managed to configure
getmail to feed into a patchwork instance exactly once, and found
configuring postfix so daunting that I actually suggested just using an
email-as-a-service provider to take the hassle out of things [1].
Anything that lets one avoid working with those tools is a good thing
in my mind.

Stephen

[1] https://patchwork.readthedocs.io/en/latest/deployment/installation/#use-a-email-as-a-service-provider