)]}'
{
  "commit": "db30130165bef1ceff04c0163db6676db23ba2fc",
  "tree": "d7b6af581ec2ec9309f0021a131b024db52f3216",
  "parents": [
    "b637a41ebe0e65b6d64dd65efaf848b4705dcbed"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Sat Jun 17 01:15:59 2023 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Sat Jun 17 09:08:31 2023 -0700"
  },
  "message": "http: handle both \"h2\" and \"h2h3\" in curl info lines\n\nWhen redacting auth tokens in trace output from curl, we look for http/2\nheaders of the form \"h2h3 [header: value]\". This comes from b637a41ebe\n(http: redact curl h2h3 headers in info, 2022-11-11).\n\nBut the \"h2h3\" prefix changed to just \"h2\" in curl\u0027s fc2f1e547 (http2:\nsupport HTTP/2 to forward proxies, non-tunneling, 2023-04-14). That\u0027s in\nreleased version curl 8.1.0; linking against that version means we\u0027ll\nfail to correctly redact the trace. Our t5559.17 notices and fails.\n\nWe can fix this by matching either prefix, which should handle both old\nand new versions.\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": "8a5ba3f47769424e8315658b1f14903cc4957ecf",
      "old_mode": 33188,
      "old_path": "http.c",
      "new_id": "f30bd0bca9bf2aa0574cf0e1738d2454d24b19e7",
      "new_mode": 33188,
      "new_path": "http.c"
    }
  ]
}