)]}'
{
  "commit": "d53ad0b07d3e7bdd2668c2d3f1815d95d4b8f532",
  "tree": "6d2ee0246583eb37ec60acc5c538a37ebb4a3989",
  "parents": [
    "535e0089e0656fd4fcaa36ad5abc3653a9a45ff0"
  ],
  "author": {
    "name": "Ian Wienand",
    "email": "iwienand@redhat.com",
    "time": "Thu Feb 20 13:55:13 2014 +1100"
  },
  "committer": {
    "name": "Ian Wienand",
    "email": "iwienand@redhat.com",
    "time": "Mon Feb 24 09:35:19 2014 +1100"
  },
  "message": "Add GIT_TIMEOUT variable to watch git operations\n\nDuring my CI testing of each devstack change I can often see git get\nitself stuck and hang indefinitely.  I\u0027m not sure if it\u0027s transient\nnetwork issues, or issues at the remote end (seen with both github.com\nand git.openstack.org) but it hits fairly frequently.  Retrying the\ncommand usually gets it going again.  Searching for \"git hanging\" and\nsimilar shows its not entirely uncommon...\n\nThis adds a watchdog timeout for remote git operations based on a new\nenvironment variable GIT_TIMEOUT.  It will retry 3 times before giving\nup.  The wrapper is applied to the main remote git calls.\n\nChange-Id: I5b0114ca26b7ac2f25993264f761cba9ec8c09e1\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d92e39cd91dae8da39a771cfdd9c2f5f71b02b47",
      "old_mode": 33188,
      "old_path": "functions-common",
      "new_id": "9cd5acd47bb5aaaff835fe79f39557f51bd3bdd5",
      "new_mode": 33188,
      "new_path": "functions-common"
    },
    {
      "type": "modify",
      "old_id": "56fa40269c5bff3ea5cb2eca97c43e66299a9869",
      "old_mode": 33188,
      "old_path": "stackrc",
      "new_id": "8cec09eb28eaa0758c5bc16cef69dfa0c0a7f850",
      "new_mode": 33188,
      "new_path": "stackrc"
    }
  ]
}