)]}'
{
  "commit": "98a136474082cdc7228d7e0e45672c5274fab701",
  "tree": "008d37ad3da3f53594d21a992a92ad1bda10aa98",
  "parents": [
    "b994622632154fc3b17fb40a38819ad954a5fb88"
  ],
  "author": {
    "name": "Emily Shaffer",
    "email": "emilyshaffer@google.com",
    "time": "Tue May 12 14:44:20 2020 -0700"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue May 12 15:30:39 2020 -0700"
  },
  "message": "trace2: log progress time and throughput\n\nRather than teaching only one operation, like \u0027git fetch\u0027, how to write\ndown throughput to traces, we can learn about a wide range of user\noperations that may seem slow by adding tooling to the progress library\nitself. Operations which display progress are likely to be slow-running\nand the kind of thing we want to monitor for performance anyways. By\nshowing object counts and data transfer size, we should be able to\nmake some derived measurements to ensure operations are scaling the way\nwe expect.\n\nSigned-off-by: Emily Shaffer \u003cemilyshaffer@google.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "75633e9c5e91a959e624ea38898933ea20d1daaa",
      "old_mode": 33188,
      "old_path": "progress.c",
      "new_id": "6d2dcff0b6920037463f217d3d699305e8ccc491",
      "new_mode": 33188,
      "new_path": "progress.c"
    },
    {
      "type": "modify",
      "old_id": "d2d088d9a0c31752739e1fdb118677278aabaf4f",
      "old_mode": 33261,
      "old_path": "t/t0500-progress-display.sh",
      "new_id": "1ed1df351cb178562d21ab204f2b5c85d3206ba2",
      "new_mode": 33261,
      "new_path": "t/t0500-progress-display.sh"
    }
  ]
}