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

[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 introduced.
>>>
>>> Updated REST API version to 1.2
 ....
>>> Mete Polat (5):
>>>   Add option to get all project patches in one mbox
>>>   Add urls to get all project patches in one mbox
>>>   Add api endpoint for project patches as mbox
>>>   Update api documentation for v1.2
>>>   Add release notes: project patches as mbox
>>>
>>>  docs/api/rest/index.rst                       |   50 +-
>>>  docs/api/rest/schemas/v1.1.rst                |    4 +-
>>>  docs/api/rest/schemas/v1.2.rst                |    5 +
>>>  docs/api/schemas/generate_schema.py           |    4 +-
>>>  docs/api/schemas/latest/patchwork.yaml        |    7 +-
>>>  docs/api/schemas/patchwork.j2                 |    7 +
>>>  docs/api/schemas/v1.2/patchwork.yaml          | 2319 +++++++++++++++++
>> 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)?
>>
Reminder.    I  hope it helps this cool project.


Geert Stappers