)]}'
{
  "commit": "30325e23ba0d40567cc4ef78e4ba0c3776ef0c06",
  "tree": "f8c265d25c9264bcc348ee905288cdfc2363af10",
  "parents": [
    "6f11c42e8edc5cf7d65156c9dd68e720f1b92229"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Wed Jun 04 16:55:52 2025 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Jun 04 14:17:53 2025 -0700"
  },
  "message": "curl: fix integer variable typechecks with curl_easy_setopt()\n\nAs discussed in the previous commit, 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\nThat patch fixed integer constants by adding an \"L\". This one deals with\nactual variables.\n\nArguably these variables could just be declared as \"long\" in the first\nplace. But it\u0027s actually kind of awkward due to other code which uses\nthem:\n\n  - port is conceptually a short, and we even call htons() on it (though\n    weirdly it is defined as a regular int).\n\n  - ssl_verify is conceptually a bool, and we assign to it from\n    git_config_bool().\n\nSo I think we could probably switch these out for longs without hurting\nanything, but it just feels a bit weird. Doubly so because if you don\u0027t\nset USE_CURL_FOR_IMAP_SEND set, then the current types are fine!\n\nSo let\u0027s just cast these to longs in the curl calls, which makes what\u0027s\ngoing on obvious. There aren\u0027t that many spots to modify (and as you can\nsee from the context, we already have some similar casts).\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": "27dc033c7f8e33afe69076b3d4f8ef91d35ee109",
      "old_mode": 33188,
      "old_path": "imap-send.c",
      "new_id": "2e812f5a6e9e10d187507fa4458606bd5867680a",
      "new_mode": 33188,
      "new_path": "imap-send.c"
    }
  ]
}