)]}'
{
  "commit": "30c586ff15935d4439ab31f9ab8424f28e6b461e",
  "tree": "4efed1edc2e056fcc89e5aaebc78220eb54df904",
  "parents": [
    "95d67879735cfecfdd85f89e59d993c5b4de8835"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Fri Jul 28 17:47:48 2017 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Jul 28 15:48:39 2017 -0700"
  },
  "message": "t/lib-proto-disable: restore protocol.allow after config tests\n\nThe tests for protocol.allow actually set that variable in\nthe on-disk config, run a series of tests, and then never\nclean up after themselves. This means that whatever tests we\nrun after have protocol.allow\u003dnever, which may influence\ntheir results.\n\nIn most cases we either exit after running these tests, or\ndo another round of test_proto(). In the latter case, this happens to\nwork because:\n\n  1. Tests of the GIT_ALLOW_PROTOCOL environment variable\n     override the config.\n\n  2. Tests of the specific config \"protocol.foo.allow\"\n     override the protocol.allow config.\n\n  3. The next round of protocol.allow tests start off by\n     setting the config to a known value.\n\nHowever, it\u0027s a land-mine waiting to trap somebody adding\nnew tests to one of the t581x test scripts. Let\u0027s make sure\nwe clean up after ourselves.\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": "02f49cb4097153f84d5e397b1801128e229c7909",
      "old_mode": 33188,
      "old_path": "t/lib-proto-disable.sh",
      "new_id": "83babe57d959005315ed0780caced285b440e8bc",
      "new_mode": 33188,
      "new_path": "t/lib-proto-disable.sh"
    }
  ]
}