)]}'
{
  "commit": "d8fab07208abfbe7dc93aea97c5577cdd73266c5",
  "tree": "81bd5b86e323fc49f14e1ab749eba59989f6de3b",
  "parents": [
    "eb9d47cf9b1cb36876df1cfd48ab57278729be6d"
  ],
  "author": {
    "name": "Tay Ray Chuan",
    "email": "rctay89@gmail.com",
    "time": "Thu Apr 08 10:15:18 2010 +0800"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Apr 09 21:16:11 2010 -0700"
  },
  "message": "remote-curl: ensure that URLs have a trailing slash\n\nPreviously, we blindly assumed that URLs passed to the remote-curl\nhelper did not end with a trailing slash.\n\nUse the convenience function end_url_with_slash() from http.[ch] to\nensure that URLs have a trailing slash on invocation of the remote-curl\nhelper, and use the URL as one with a trailing slash throughout.\n\nIt is possible for users to pass a URL with a trailing slash to\nremote-curl, by, say, setting it in remote.\u003cname\u003e.url in their git\nconfig. The resulting requests have an empty path component (//) and may\nbreak implementations of the http git protocol.\n\nSigned-off-by: Tay Ray Chuan \u003crctay89@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a904164e425097380781c1ecd9bb13f4feec0de6",
      "old_mode": 33188,
      "old_path": "remote-curl.c",
      "new_id": "1fe59d6db0e85ab938959f08d3bca4a83f748ab5",
      "new_mode": 33188,
      "new_path": "remote-curl.c"
    },
    {
      "type": "modify",
      "old_id": "7873d9429ab86292c03f7704b5b0d919e1a7f029",
      "old_mode": 33261,
      "old_path": "t/t5541-http-push.sh",
      "new_id": "f0c50d3d774dcbd2449988c65e0813cf25366b89",
      "new_mode": 33261,
      "new_path": "t/t5541-http-push.sh"
    }
  ]
}
