)]}'
{
  "commit": "4558c8f84b2f8d3ba1483727bcb49935ae8ff595",
  "tree": "0a5b106fac9cea0ad047863223a2c3dc8739f639",
  "parents": [
    "30325e23ba0d40567cc4ef78e4ba0c3776ef0c06"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Wed Jun 04 16:56:22 2025 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Jun 04 14:17:53 2025 -0700"
  },
  "message": "curl: fix symbolic constant typechecks with curl_easy_setopt()\n\nAs with the previous two commits, we should be passing long integers,\nnot regular ones, to curl_easy_setopt(), and compiling against curl 8.14\nloudly complains if we don\u0027t.\n\nThis patch catches the remaining cases, which are ones where we pass\ncurl\u0027s own symbolic constants. We\u0027ll cast them to long manually in each\ncall.\n\nIt seems kind of weird to me that curl doesn\u0027t define these constants as\nlongs, since the point of them is to pass to curl_easy_setopt(). But in\nthe curl documentation and examples, they clearly show casting them as\npart of the setopt calls. It may be that there is some reason not to\npush the type into the macro, like backwards compatibility. I didn\u0027t\ndig, as it doesn\u0027t really matter: we have to follow what existing curl\nversions ask for anyway.\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": "cce2ea7287368703da0d0f2766d77e715ef39343",
      "old_mode": 33188,
      "old_path": "http.c",
      "new_id": "ecbc47ea4b3f27e03607fdb982f392ace3b209ae",
      "new_mode": 33188,
      "new_path": "http.c"
    }
  ]
}