)]}'
{
  "commit": "c308b9c25d54c72977d16155ae04e37f3490d5ac",
  "tree": "c5a6f4f9019e336df06c73f244f827d542402f08",
  "parents": [
    "f78683f3a85ca16ae16e1180703d3280b272f45d"
  ],
  "author": {
    "name": "Will Palmer",
    "email": "wmpalmer@gmail.com",
    "time": "Sat Apr 17 17:55:26 2010 +0100"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Sat Apr 17 11:50:32 2010 -0700"
  },
  "message": "documentation: clarify direction of core.autocrlf\n\nThe description for core.autocrlf refers to reads from / writes to\n\"the filesystem\", the only use of this rather ambiguous term, which\ntechnically could be referring to the git object database. (All other\nmentions are part of phrases such as \"..filesystems (like NFS)..\").\n\nOther sections, including the section on core.safecrlf, use the term\n\"work tree\" for the same purpose as the term \"the filesystem\" is used in\nthe core.autocrlf section, so that seems like a good alternative, which\nmakes it clearer what direction the addition/removal of CR characters\noccurs in.\n\nSigned-off-by: Will Palmer \u003cwmpalmer@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "75b8afec09aa490f707d2b7abcc40e96f416bfac",
      "old_mode": 33188,
      "old_path": "Documentation/config.txt",
      "new_id": "f6ddd35c01ae0f0adb7b10c70649b2e2c14667fd",
      "new_mode": 33188,
      "new_path": "Documentation/config.txt"
    }
  ]
}