)]}'
{
  "commit": "a94cf2cb7e77c27ce5c3d648e37c1aa75cd5e56e",
  "tree": "eabaeaa47f6013fcab6d86985b763a0e2407a588",
  "parents": [
    "04a74b6cfa5ef4870263f84ac94a488d9f2ef14a"
  ],
  "author": {
    "name": "Brandon Casey",
    "email": "drafnel@gmail.com",
    "time": "Tue Jun 18 19:43:49 2013 -0700"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Jun 19 10:00:26 2013 -0700"
  },
  "message": "http.c: don\u0027t rewrite the user:passwd string multiple times\n\nCurl older than 7.17 (RHEL 4.X provides 7.12 and RHEL 5.X provides\n7.15) requires that we manage any strings that we pass to it as\npointers.  So, we really shouldn\u0027t be modifying this strbuf after we\nhave passed it to curl.\n\nOur interaction with curl is currently safe (before or after this\npatch) since the pointer that is passed to curl is never invalidated;\nit is repeatedly rewritten with the same sequence of characters but\nthe strbuf functions never need to allocate a larger string, so the\nsame memory buffer is reused.\n\nThis \"guarantee\" of safety is somewhat subtle and could be overlooked\nby someone who may want to add a more complex handling of the username\nand password.  So, let\u0027s stop modifying this strbuf after we have\npassed it to curl, but also leave a note to describe the assumptions\nthat have been made about username/password lifetime and to draw\nattention to the code.\n\nSigned-off-by: Brandon Casey \u003cdrafnel@gmail.com\u003e\nAcked-by: Jeff King \u003cpeff@peff.net\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d9d1aad3be468394e39966c0b45e7e101b387b0c",
      "old_mode": 33188,
      "old_path": "http.c",
      "new_id": "c02246a78b954569e9c6d5757f7ffe7464e97424",
      "new_mode": 33188,
      "new_path": "http.c"
    }
  ]
}