)]}'
{
  "commit": "2c620a1ad1dce1e249d66ce18c7b1cce22d5d64c",
  "tree": "c92dc1ebdc6b9f6b27c60d31de1cc8823b009a3f",
  "parents": [
    "941c9449999192e2d338ee204f4153e30ae43829"
  ],
  "author": {
    "name": "Michal Ostrowski",
    "email": "mostrows@watson.ibm.com",
    "time": "Fri Jan 20 13:05:24 2006 -0500"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "junkio@cox.net",
    "time": "Tue Jan 24 23:17:26 2006 -0800"
  },
  "message": "git-fetch: pass --upload-pack to fetch-pack\n\nWithout this, there is no way to specify a remote executable when\ninvoking git-pull/git-fetch as there is for git-clone.\n\n[jc: I have a mild suspicion that this is a broken environment (aka\n sysadmin disservice).  It may be legal to configure your sshd to\n spawn named program without involving shell at all, and if your\n sysadmin does so and you have your git programs under your home\n directory, you would need something like this, but then I suspect\n you would need such workaround everywhere, not just git. But we\n have these options we can use to work around the issue, so there\n is no strong reason not to reject this patch, either. ]\n\nSigned-off-by: Michal Ostrowski \u003cmostrows@watson.ibm.com\u003e\nSigned-off-by: Junio C Hamano \u003cjunkio@cox.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e624d3d0ee93c5d1618bf220ecd2d4eafddc47ca",
      "old_mode": 33188,
      "old_path": "Documentation/fetch-options.txt",
      "new_id": "83237562d2ba2a8891f06646ab65c0b4817e225e",
      "new_mode": 33188,
      "new_path": "Documentation/fetch-options.txt"
    },
    {
      "type": "modify",
      "old_id": "4a0cb32f308742faf0f1ab4d023025ab3602ad31",
      "old_mode": 33261,
      "old_path": "git-fetch.sh",
      "new_id": "d1659e2cfe78fef5bd8712edcedbf7296eb316be",
      "new_mode": 33261,
      "new_path": "git-fetch.sh"
    }
  ]
}