)]}'
{
  "commit": "6d1700b8af43ea6078c8f17dedc0613431f6b07d",
  "tree": "3735997037cd4842329078e6eb257c366b5b64a2",
  "parents": [
    "9752ad0bb79f680bca48db7adc45338b298304b0"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Nov 09 11:49:45 2017 +0900"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Nov 09 12:28:30 2017 +0900"
  },
  "message": "merge-base --fork-point doc: clarify the example and failure modes\n\nThe illustrated history used to explain the `--fork-point` mode\nnamed three keypoint commits B3, B2 and B1 from the oldest to the\nnewest, which was hard to read.  Relabel them to B0, B1, B2.  Also\nillustrate the history after the rebase using the `--fork-point`\nfacility was made.\n\nThe text already mentions use of reflog, but the description is not\nclear what benefit we are trying to gain by using reflog.  Clarify\nthat it is to find the commits that were known to be at the tip of\nthe remote-tracking branch.  This in turn necessitates users to know\nthe ramifications of the underlying assumptions, namely, expiry of\nreflog entries will make it impossible to determine which commits\nwere at the tip of the remote-tracking branches and we fail when in\ndoubt (instead of giving a random and incorrect result without even\nwarning).  Another limitation is that it won\u0027t be useful if you did\nnot fork from the tip of a remote-tracking branch but from in the\nmiddle.\n\nDescribe them.\n\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b968b64c380b4fbe2663da42355fc9e8fdd24679",
      "old_mode": 33188,
      "old_path": "Documentation/git-merge-base.txt",
      "new_id": "502e00ec35ff1fd543dbd8361a317cb583ca1eba",
      "new_mode": 33188,
      "new_path": "Documentation/git-merge-base.txt"
    }
  ]
}