)]}'
{
  "commit": "2f56f56ad991edd51ffd0baf1182245ee1277a04",
  "tree": "e4062e2bb1a92b487609cded256d5ede1a6eda90",
  "parents": [
    "efa4c1206eaff047c474af2136748a58eb8cc33b"
  ],
  "author": {
    "name": "Sage Weil",
    "email": "sage@newdream.net",
    "time": "Wed Oct 27 20:59:49 2010 -0700"
  },
  "committer": {
    "name": "Sage Weil",
    "email": "sage@newdream.net",
    "time": "Wed Oct 27 21:05:54 2010 -0700"
  },
  "message": "Revert \"ceph: update issue_seq on cap grant\"\n\nThis reverts commit d91f2438d881514e4a923fd786dbd94b764a9440.\n\nThe intent of issue_seq is to distinguish between mds-\u003eclient messages that\n(re)create the cap and those that do not, which means we should _only_ be\nupdating that value in the create paths.  By updating it in handle_cap_grant,\nwe reset it to zero, which then breaks release.\n\nThe larger question is what workload/problem made me think it should be\nupdated here...\n\nSigned-off-by: Sage Weil \u003csage@newdream.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "98ab13e2b71d9d8ebcbf1715da112d78cb0bac17",
      "old_mode": 33188,
      "old_path": "fs/ceph/caps.c",
      "new_id": "6e0942f33dd81884483a08dce13b3c8f84c796d6",
      "new_mode": 33188,
      "new_path": "fs/ceph/caps.c"
    }
  ]
}