)]}'
{
  "commit": "10c497aa0cc7ccb5bd213f53fc0cd803bd73a508",
  "tree": "d6820a550c72b2d52432df90b47808f1ca3c9a6f",
  "parents": [
    "7fa1365c54c28b3cd9375539f381b54061a1880d"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Wed Dec 10 05:40:07 2014 -0500"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Dec 10 09:27:24 2014 -0800"
  },
  "message": "read_packed_refs: use a strbuf for reading lines\n\nCurrent code uses a fixed PATH_MAX-sized buffer for reading\npacked-refs lines. This is a reasonable guess, in the sense\nthat git generally cannot work with refs larger than\nPATH_MAX.  However, there are a few cases where it is not\ngreat:\n\n  1. Some systems may have a low value of PATH_MAX, but can\n     actually handle larger paths in practice. Fixing this\n     code path probably isn\u0027t enough to make them work\n     completely with long refs, but it is a step in the\n     right direction.\n\n  2. We use fgets, which will happily give us half a line on\n     the first read, and then the rest of the line on the\n     second. This is probably OK in practice, because our\n     refline parser is careful enough to look for the\n     trailing newline on the first line. The second line may\n     look like a peeled line to us, but since \"^\" is illegal\n     in refnames, it is not likely to come up.\n\n     Still, it does not hurt to be more careful.\n\nSigned-off-by: Jeff King \u003cpeff@peff.net\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "82e5b1b14f7a6e7341dfcf8fbf61ae3982851e18",
      "old_mode": 33188,
      "old_path": "refs.c",
      "new_id": "60a7e33d5b1bad9000d2a230eac09190fa858c85",
      "new_mode": 33188,
      "new_path": "refs.c"
    }
  ]
}