)]}'
{
  "commit": "d88263dc86a37918cc86b014353a3cf4c6c8e3c2",
  "tree": "441f2e5e5651ca2c42a5062499563f36908a60a2",
  "parents": [
    "e70a87194b6758be8ea0458ed06a3f5ac4865a94"
  ],
  "author": {
    "name": "Barret Rhoden",
    "email": "brho@cs.berkeley.edu",
    "time": "Mon Mar 20 18:19:10 2017 -0400"
  },
  "committer": {
    "name": "Barret Rhoden",
    "email": "brho@cs.berkeley.edu",
    "time": "Tue Mar 21 14:29:06 2017 -0400"
  },
  "message": "strace: Handle variable-width timestamps\n\nIf a machine has an uptime of over 10 million seconds (about 4 months),\nthen the timestamp field grows.  Strace couldn\u0027t handle this, since it\nassumed the field was 40 bytes.\n\nIncidentally, the machine wasn\u0027t up for 120 days, but it might have not\nbeen turned off in that long.  Sometimes (often?) soft reboots don\u0027t reset\nthe TSC, which is where that timestamp comes from.  This occurence is the\nsame reason I found the bug from commit fd20de73987b (\"Fixes TCP drops due\nto ARP timeouts\").\n\nSigned-off-by: Barret Rhoden \u003cbrho@cs.berkeley.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f693009705b67881015125cec7fe395848166eac",
      "old_mode": 33188,
      "old_path": "tests/strace.c",
      "new_id": "3ff8fc8289ea8395068819fb80f0de24d494200e",
      "new_mode": 33188,
      "new_path": "tests/strace.c"
    }
  ]
}