)]}'
{
  "commit": "0e418e568f4104ce1915263ae3ad66e290eebed8",
  "tree": "e929db0b7b2b30d1c9e5003dae01a9c381e01996",
  "parents": [
    "c30e742c4981585061ed52c14abd9ebd32a0e18b"
  ],
  "author": {
    "name": "Johannes Sixt",
    "email": "j6t@kdbg.org",
    "time": "Fri Jul 09 09:05:16 2010 +0200"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Jul 09 16:27:31 2010 -0700"
  },
  "message": "t0005: work around strange $? in ksh when program terminated by a signal\n\nksh93 is known to report $? of programs that terminated by a signal as\n256 + signal number instead of 128 + signal number like other POSIX\ncompliant shells (ksh\u0027s behavior is still POSIX compliant in this regard).\n\nSigned-off-by: Johannes Sixt \u003cj6t@kdbg.org\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "09f855af3e9cded903c828f3f946a0c2403ddcdf",
      "old_mode": 33261,
      "old_path": "t/t0005-signals.sh",
      "new_id": "93e58c00e886db22b5ebf86af103efc4e65ec832",
      "new_mode": 33261,
      "new_path": "t/t0005-signals.sh"
    }
  ]
}