{"ref":"refs/heads/rw2","commits":[{"author":{"name":"Marc Dionne","email":"691713f3160d0cd1be0d99227e42692818432913@gmail.com"},"url":"https://api.github.com/repos/mdionne/openafs/commits/764cbb4400045b30ff60e78ac8ad46a580950917","message":"RW: fix incorrect logging\n\nChange-Id: I30fb6d786270e05fd1b215ce9efe9c4b036842db","sha":"764cbb4400045b30ff60e78ac8ad46a580950917"},{"author":{"name":"Marc Dionne","email":"691713f3160d0cd1be0d99227e42692818432913@gmail.com"},"url":"https://api.github.com/repos/mdionne/openafs/commits/3230a554127fe0c4ab58f8bd9133468fcc947573","message":"RW replication: Insert RemoveFile op into list before releasing locks\n\nIn order to insure that updates are inserted into the queue in the\ncorrect order, we need to do so before releasing the lock on the\nvnode in PutVolumePackage.  Otherwise, a later update touching the\nsame vnode might get inserted before us and sent to the slaves in\nthe wrong order.  The oberved case was a RemoveFile on a Vnode\nfollowed by a CreateFile that is given the same Vnode.\n\nA similar change will be needed for some other operations.\n\nChange-Id: I43c0f89d68dc73e43de8cfe08ab30b15f2c84913","sha":"3230a554127fe0c4ab58f8bd9133468fcc947573"}],"head":"3230a554127fe0c4ab58f8bd9133468fcc947573","size":2,"push_id":49709488}