)]}'
{
  "commit": "26d22dc64ad2373eb918f004a1d0ba2649e7e1a5",
  "tree": "b968fa9f467c8457f039f7a2c155469f2687a03b",
  "parents": [
    "167d7445433bb6dfac6b844b99ae455129326141"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Mon Apr 13 07:18:52 2009 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Mon Apr 13 09:04:50 2009 -0700"
  },
  "message": "doc/checkout: refer to git-branch(1) as appropriate\n\nMost of description for the branch creation options is\nsimply cut and paste from git-branch. There are two reasons\nto fix this:\n\n  1. It can grow stale with respect to what\u0027s in \"git\n     branch\" (which it is now is).\n\n  2. It is not just an implementation detail, but rather the\n     desired mental model for the command that we are using\n     \"git branch\" here. Being explicit about that can help\n     the user understand what is going on.\n\nIt also makes sense to strip the branch creation options\nfrom the synopsis, as they are making it a long,\nhard-to-read line. They are still easily discovered by\nreading the options list, and --track is explicitly\nreferenced when branch creation is described.\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": "16d3c872a056eed29806d96e4de2544963df72bd",
      "old_mode": 33188,
      "old_path": "Documentation/git-checkout.txt",
      "new_id": "22ad10d9522c221a87c7177db7196ad95c6f9430",
      "new_mode": 33188,
      "new_path": "Documentation/git-checkout.txt"
    }
  ]
}