)]}'
{
  "commit": "c2c6d9302a98ae4c4c76822a1c83551c039271a0",
  "tree": "dfa55cde4bdfd246d6d089f407edc1fe0534cf02",
  "parents": [
    "3e63e0df4f1a1610782e679be56ea75f820343fc"
  ],
  "author": {
    "name": "Gerrit Pape",
    "email": "pape@smarden.org",
    "time": "Thu Mar 29 06:42:44 2007 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "junkio@cox.net",
    "time": "Thu Mar 29 01:38:28 2007 -0700"
  },
  "message": "Documentation/git-rev-parse.txt: fix example in SPECIFYING RANGES.\n\nPlease see http://bugs.debian.org/404795:\n\n In git-rev-parse(1), there is an example commit tree, which is used twice.\n The explanation for this tree is very clear: B and C are commit *parents* to\n A.\n\n However, when the tree is reused as an example in the SPECIFYING RANGES, the\n manpage author screws up and uses A as a commit *parent* to B and C!  I.e.,\n he inverts the tree.\n\n And the fact that for this example you need to read the tree backwards is\n not explained anywhere (and it would be confusing even if it was).\n\nSigned-off-by: Gerrit Pape \u003cpape@smarden.org\u003e\nSigned-off-by: Junio C Hamano \u003cjunkio@cox.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4041a1607081ee6e8d93065c67fc72a513c20b17",
      "old_mode": 33188,
      "old_path": "Documentation/git-rev-parse.txt",
      "new_id": "d0a2ad30884e2d7d148474d49030db5a7820bc29",
      "new_mode": 33188,
      "new_path": "Documentation/git-rev-parse.txt"
    }
  ]
}