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

Daniel Axtens dja at axtens.net
Fri Jul 5 23:04:54 AEST 2019

>>> 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.

For what it's worth, what to do in future if you have a large patch is:

 1) send the patches that you can to the list as regular mail

 2) include in your cover letter a link to a signed tag that we can pull
    to get the patches that do not make it to the list.

Please make sure that patches that cannot go to the list are as simple
to review as possible (e.g. automatically generated) because they miss
out on review on the list.

In this case I don't think you'll end up needing to resend that patch
because I think we landed on a management command rather than changing
the API, but maybe it will help in future.


> Geert Stappers
> _______________________________________________
> Patchwork mailing list
> Patchwork at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/patchwork

More information about the Patchwork mailing list