On Sat, 2016-11-19 at 16:51 +0000, Stephen Finucane wrote:
> Adopt a hybrid approach, by adding an additional series endpoint to the
> existing patch endpoint:
>
> /series/${series_id}/
> /patches/${patch_id}/
>
> This is based on the approach described here:
>
> http://softwareengineering.stackexchange.com/a/275007/106804
>
> This is necessary due to the N:N mapping of series and patches: it's
> possible for a patch to belong to many series, and a series usually
> contains many patches. This means it is not possible to rely on the
> patch endpoint alone.
>
> It is also necessary to add a cover letter endpoint, such that the
> series body can include this.
>
> Signed-off-by: Stephen Finucane <[email protected]>
> Cc: Andy Doan <[email protected]>
>
Currently the url field points to /project/<id>/ rather than /series/<id>/, and
there's no reference to the project that the series belongs to, which would be
nice.
Also to be clear, the patches array is guaranteed to be in order, right?
_______________________________________________
Patchwork mailing list
[email protected]
https://lists.ozlabs.org/listinfo/patchwork
