{"push_id":828965832,"size":1,"distinct_size":1,"ref":"refs/heads/fix5","head":"9e73fb4c30ce6acc03c9e5a0beced89cef072a3d","before":"87f8055da746ee05bb29a75c8495debc35db6fd1","commits":[{"sha":"9e73fb4c30ce6acc03c9e5a0beced89cef072a3d","author":{"email":"bea13b40ec72713ddcfa070741018e0feab937d4@mindspring.com","name":"Frank S. Filz"},"message":"Allow SETCLIENTD if a confirmed clientid exists and principal doesn't match\n\nAssuming the confirmed clientid has no live state associated with it,\nit is acceptable to have a new SETCLIENTID with a different principal\nper RFC 7530 Section 9.1.2. Server Release of Client ID.\n\nIf the client confirms this clientid, the old one will be expired\nand cleaned up.\n\nChange-Id: Iddc2371fab55d66c885be4a3a0de844d6b21eb93\nSigned-off-by: Frank S. Filz <ffilzlnx@mindspring.com>","distinct":true,"url":"https://api.github.com/repos/ffilz/nfs-ganesha/commits/9e73fb4c30ce6acc03c9e5a0beced89cef072a3d"}]}