)]}'
{
  "commit": "4ecbc178704ca6c1027a38483e98f5fe493b1322",
  "tree": "e5cf8b0e1e660eb837c2e5d98c2071a0a1e3bb57",
  "parents": [
    "3125be17d66e65c854249fb6a0c05322798593fe"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Thu Jul 09 02:37:35 2009 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Jul 09 01:19:51 2009 -0700"
  },
  "message": "Makefile: install \u0027git\u0027 in execdir\n\nWhen a git command executes a subcommand, it uses the \"git\nfoo\" form, which relies on finding \"git\" in the PATH.\nNormally this should not be a problem, since the same \"git\"\nthat was used to invoke git in the first place will be\nfound.  And if somebody invokes a \"git\" outside of the PATH\n(e.g., by giving its absolute path), this case is already\ncovered: we put that absolute path onto the front of PATH.\n\nHowever, if one is using \"sudo\", then sudo will execute the\n\"git\" from the PATH, but pass along a restricted PATH that\nmay not contain the original \"git\" directory. In this case,\nexecuting a subcommand will fail.\n\nTo solve this, we put the \"git\" wrapper itself into the\nexecdir; this directory is prepended to the PATH when git\nstarts, so the wrapper will always be found.\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": "78cc11382a1e5f5d4d5b403015b8071c785a8501",
      "old_mode": 33188,
      "old_path": "Makefile",
      "new_id": "311ce7d745e28af8f93dc0caade13a82fe943fb0",
      "new_mode": 33188,
      "new_path": "Makefile"
    }
  ]
}