)]}'
{
  "commit": "835c4d3689972e616bd109cec3dd8cd4aa4d4c0d",
  "tree": "da7c8b996579dfcab25af29063fc8fc6dc219bf4",
  "parents": [
    "2635c2b8bfc9aec07b7f023d8e3b3d02df715344"
  ],
  "author": {
    "name": "David Turner",
    "email": "dturner@twopensource.com",
    "time": "Mon Nov 02 16:39:58 2015 -0500"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Mon Nov 02 14:18:06 2015 -0800"
  },
  "message": "http.c: use CURLOPT_RANGE for range requests\n\nA HTTP server is permitted to return a non-range response to a HTTP\nrange request (and Apache httpd in fact does this in some cases).\nWhile libcurl knows how to correctly handle this (by skipping bytes\nbefore and after the requested range), it only turns on this handling\nif it is aware that a range request is being made.  By manually\nsetting the range header instead of using CURLOPT_RANGE, we were\nhiding the fact that this was a range request from libcurl.  This\ncould cause corruption.\n\nSigned-off-by: David Turner \u003cdturner@twopensource.com\u003e\nReviewed-by: Jeff King \u003cpeff@peff.net\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7da76edda16abea8a53299f2770ad2dce55c1b60",
      "old_mode": 33188,
      "old_path": "http.c",
      "new_id": "5f368464e8f3e3980b36b4692d095dd06d89a0d6",
      "new_mode": 33188,
      "new_path": "http.c"
    },
    {
      "type": "modify",
      "old_id": "49afe39279d02785f3567aad2fec55c623a53d5f",
      "old_mode": 33188,
      "old_path": "http.h",
      "new_id": "4f97b60b5c8abdf5ab0610382a6d6fa289df2605",
      "new_mode": 33188,
      "new_path": "http.h"
    }
  ]
}