)]}'
{
  "commit": "2810cbc7784e9a21e7001c31b65af94fd9ba7a5b",
  "tree": "d127eb13f4749cb40a4f58ce3a83985083751a8a",
  "parents": [
    "6ed4e2834639d0b08686882d2e39cd736d66c688"
  ],
  "author": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Sat Apr 18 10:09:16 2009 -0700"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Sat Apr 18 10:09:16 2009 -0700"
  },
  "message": "Only display a progress meter once we spend 0.5 seconds on a task\n\nThe point of the progress meter is to let the user know that the\ntask is progressing, and give them a chance to estimate when it will\nbe complete.  If the task completes in under 0.5 seconds then it\nis sufficiently fast enough that the user doesn\u0027t need to be kept\nup-to-date on its progress; in fact showing the meter may just slow\nthe task down waiting on the tty to redraw.\n\nWe now delay the progress meter 0.5 seconds (or 1 second if the\nPython time.time() function isn\u0027t accurate enough) to avoid any\nreally fast tasks, like a no-op local sync.\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "98bb642960cf2c659be1f76ce0a044d8cc80aaec",
      "old_mode": 33188,
      "old_path": "progress.py",
      "new_id": "b119b3741f93c3c914ec4b5fe7ab08db508c9c86",
      "new_mode": 33188,
      "new_path": "progress.py"
    }
  ]
}