)]}'
{
  "commit": "60253a605d230a7fd2b32e77e94bd620c1399b72",
  "tree": "0b4d2c93f1dd86f50442187b16750371e0e4cde7",
  "parents": [
    "fc142811d14d3acb64d1c2057a774fa1573e60cb"
  ],
  "author": {
    "name": "Sebastian Schuberth",
    "email": "sschuberth@gmail.com",
    "time": "Fri Jan 08 10:32:52 2016 +0100"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Jan 08 12:40:12 2016 -0800"
  },
  "message": "docs: clarify that --depth for git-fetch works with newly initialized repos\n\nThe original wording sounded as if --depth could only be used to deepen or\nshorten the history of existing repos. However, that is not the case. In a\nworkflow like\n\n    $ git init\n    $ git remote add origin https://github.com/git/git.git\n    $ git fetch --depth\u003d1\n\nThe newly initialized repo is properly created as a shallow repo.\n\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "92c68c3fdabafd9ac5afe74256dbd2d56218c247",
      "old_mode": 33188,
      "old_path": "Documentation/fetch-options.txt",
      "new_id": "fae1d78340933d703a65049508dc9251c9b0396a",
      "new_mode": 33188,
      "new_path": "Documentation/fetch-options.txt"
    }
  ]
}