)]}'
{
  "commit": "0763c3a2c4f21a9e81990cc5cbee4a66d4efefcb",
  "tree": "d5fff5eefbd3cdf9589ea6d4716bcced06a9151f",
  "parents": [
    "39fa527c8976da84cf70a9ea6b6d92a1fd9bd772"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Fri Sep 15 07:34:43 2023 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Sep 15 10:54:11 2023 -0700"
  },
  "message": "http: update curl http/2 info matching for curl 8.3.0\n\nTo redact header lines in http/2 curl traces, we have to parse past some\nprefix bytes that curl sticks in the info lines it passes to us. That\nchanged once already, and we adapted in db30130165 (http: handle both\n\"h2\" and \"h2h3\" in curl info lines, 2023-06-17).\n\nNow it has changed again, in curl\u0027s fbacb14c4 (http2: cleanup trace\nmessages, 2023-08-04), which was released in curl 8.3.0. Running a build\nof git linked against that version will fail to redact the trace (and as\nbefore, t5559 notices and complains).\n\nThe format here is a little more complicated than the other ones, as it\nnow includes a \"stream id\". This is not constant but is always numeric,\nso we can easily parse past it.\n\nWe\u0027ll continue to match the old versions, of course, since we want to\nwork with many different versions of curl. We can\u0027t even select one\nformat at compile time, because the behavior depends on the runtime\nversion of curl we use, not the version we build against.\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": "7f7bc85dd0b15c63f0ba103e878c5b163eea8f93",
      "old_mode": 33188,
      "old_path": "http.c",
      "new_id": "fb4ecf911fd3a8958539a0fe2cb081c3b53a865f",
      "new_mode": 33188,
      "new_path": "http.c"
    }
  ]
}