Re: [PATCH v2 0/5] Update REST API: Add 'project patches as mbox' field, missing

2019-07-05 Thread Daniel Axtens
>>> Probably too large to get unmoderated through the mailinglist. >> I agree. The patch is 72KB big. >>> Anyway: Patch 4/5 is missing. Even at >>> https://lists.ozlabs.org/pipermail/patchwork/2019-June/thread.html >>> >>> >>> How does get patch four of the five to the mailinglist(archive)? >>> >

Re: [PATCH v2 0/5] Update REST API: Add 'project patches as mbox' field, missing

2019-07-05 Thread Geert Stappers
On 01-07-2019 17:31, Mete Polat wrote: >> On 28-06-2019 17:56, Mete Polat wrote: >> >>> Patchwork already has the ability to export patches, series, covers and >>> bundles >>> as an mbox file. This patch extends that ability to projects as well. >>> Therefore >>> a new url and api field has been

Re: [PATCH v2 0/5] Update REST API: Add 'project patches as mbox' field

2019-07-05 Thread Daniel Axtens
Hi all, > The public inbox to patchwork integration would certainly be nice and > helpful for using it on mailing lists that are already set up to be > archived with public inbox, and it would make it easier to keep the > state of pasta and patchwork consistent. > > Please let us know where to fin