)]}'
{
  "commit": "496ffc74bb255efce367033d56f23f626efa4db4",
  "tree": "2686b35a234002c9824fd9fd89ce607c0d893182",
  "parents": [
    "c6cc585f9740fdf98d7068e0269f7ba8276cb24a"
  ],
  "author": {
    "name": "John Griffith",
    "email": "john.griffith@solidfire.com",
    "time": "Wed Sep 26 15:09:52 2012 -0600"
  },
  "committer": {
    "name": "John Griffith",
    "email": "john.griffith@solidfire.com",
    "time": "Wed Sep 26 15:11:11 2012 -0600"
  },
  "message": "Add timing info to volume exercises.\n\nLooking at some failures lately in Jenkins/Devstack runs and it would\nbe handy to see if failures were time-out related versus flat out failed\noperations.\n\nMore interestingly it might be worthwile to harvest the completion time\ninfo from the jenkins logs and keep track of any significant deviations\nintroduced by code changes.\n\nChange-Id: I3bbcc5b9f8a4da2fcdb9f6f70913c2d6bc6e2b9b\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5db10d39b43ffe3bfc43ca7e7ee9e3af18c2c186",
      "old_mode": 33261,
      "old_path": "exercises/volumes.sh",
      "new_id": "1c6320c07cb7436ebadffc89845f517e4bd504a8",
      "new_mode": 33261,
      "new_path": "exercises/volumes.sh"
    }
  ]
}