Handling multiple patches with the same hash in pwclient?

[Tom Rini]

Hey,

I've got a bug report that I found over a common for me case over in
U-Boot.

I took the post-commit git hook and made a short shell script out of it,
to keep patchwork up to date between releases, for our maintainers that
don't use patchwork directly.  This works fine in most cases, but
sometimes fails because more than one patch has the same hash.  For
example:
http://patchwork.ozlabs.org/project/uboot/patch/20200512093901.14831-2-peng.fan@nxp.com/
http://patchwork.ozlabs.org/project/uboot/patch/20200526233350.25190-1-festevam@gmail.com/
give the same hash of "a75890825af3de9740f2d0c5527a72fa33583ae6" and so
doing something like:
pwclient info -h a75890825af3de9740f2d0c5527a72fa33583ae6

fails because there's two valid results, not one.  I see some commands
support being told to return only the first (or last) N matches, but not
info.  I assume something on the server side would need changing here,
rather than the client side, after a quick peek around in pwclient
sources.  But perhaps I missed something?  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20200623/88a5d8a8/attachment.sig>