[PATCH] parsemail: Clarify exit codes

jk reports that the patchwork error codes are really unhelpful for correct integration with an MDA. In particular they make sorting out failures into a separate queue very difficult. Make this better and clearer: only return 1 on a genuinely unexpected case that requires adminstrator intervention.

Re: Patchwork 3: potential feature removals

Stephen Finucane writes: > On Thu, 2018-03-22 at 10:17 +1100, Daniel Axtens wrote: >> Hi all, >> >> Patchwork is currently quite complex. This is adding to the bug surface >> and impacting reliablity - which as the recent issues have >> reinforced, is a fundamental feature

Re: [PATCH v4] api: Add comments to patch and cover endpoints

- Original Message - > From: "Daniel Axtens" > To: vkaba...@redhat.com, patchwork@lists.ozlabs.org > Sent: Monday, April 30, 2018 6:55:11 PM > Subject: Re: [PATCH v4] api: Add comments to patch and cover endpoints > > Apologies if this is a silly question, but I was

Re: [PATCH v4] api: Add comments to patch and cover endpoints

Apologies if this is a silly question, but I was looking at this to check the perfomance, and I noticed that in the patch list endpoint (/api/patches/), it seems to be linking to the 'covers' comments endpoint rather than the 'patches' api endpoint: ... "delegate": null, "mbox":

Re: [PATCH 4/6] docker-compose: Switch to 3.0 syntax

Stephen Finucane writes: > Ubuntu 18.04 (Bionic Beaver) providers 'docker-compose' 1.17.1 [1] at > release which supports the 3.0 syntax [2]. Using this allows some users > (me) to resolve a long standing issue caused by a UID that's not 1000. > > [1]