If multiple patches have the same hash, pwclient does not take any

[YasLbk]

pwclient info -h 4a47f1233259930c1e9c532d8c5c0acbf2ae213b
No patch has the hash provided

git-pw patch list --hash 4a47f1233259930c1e9c532d8c5c0acbf2ae213b
+------+-------------+-----------------------------------------------------------------+----------------------------------------------+---------+------------+------------+
|   ID | Date        | Name                                                            | Submitter                                    | State   | Archived   | Delegate   |
|------+-------------+-----------------------------------------------------------------+----------------------------------------------+---------+------------+------------|
| 1928 | a week ago  | [v2,46/46] utils: merge  | jp (jxxxxxxx.com)                    | new     | no         |            |
| 4646 | 2 weeks ago | [45/45] utils: merge     | jp (jxxxxxxx..com)                   | new     | no         |            |
+------+-------------+-----------------------------------------------------------------+----------------------------------------------+---------+------------+------------+

[stephenfin]

This is unfortunately necessary to ensure behaviour is consistent between the XML-RPC API backend and the REST API backend, as you can see here (the XML-RPC API will not return anything if it finds more than one patch matching a hash). We can change this but it's going to need a release note.