)]}'
{
  "commit": "14516c3a30e256e8d4e7a9af271c8df644ac3222",
  "tree": "ed8d43d6568fca893b7b1ebd7bc38244fc37a409",
  "parents": [
    "0a8ebba943dd89bdd57c5dab5a66932f690847d9"
  ],
  "author": {
    "name": "Trond Myklebust",
    "email": "Trond.Myklebust@netapp.com",
    "time": "Sat Jul 31 14:29:06 2010 -0400"
  },
  "committer": {
    "name": "Trond Myklebust",
    "email": "Trond.Myklebust@netapp.com",
    "time": "Tue Aug 03 22:06:42 2010 -0400"
  },
  "message": "NFSv4.1: Handle NFS4ERR_DELAY on SEQUENCE correctly\n\nIn RFC5661, an NFS4ERR_DELAY error on a SEQUENCE operation has the special\nmeaning that the server is not finished processing the request. In this\ncase we want to just retry the request without touching the slot.\n\nAlso fix a bug whereby we would fail to update the sequence id if the\nserver returned any error other than NFS_OK/NFS4ERR_DELAY.\n\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d6413b48b0572df6a0569946d428adcc28368ab3",
      "old_mode": 33188,
      "old_path": "fs/nfs/nfs4proc.c",
      "new_id": "cab0eb9151450ed460446c2fdbcdbd01484e9f61",
      "new_mode": 33188,
      "new_path": "fs/nfs/nfs4proc.c"
    }
  ]
}
