From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Fri, 06 Jun 2025 14:27:34 GMT
Subject: Re: [PATCH v2 0/4] curl: pass long values where expected
Message-ID: <bf919293-562f-4572-bc0a-aad7f22d1013@app.fastmail.com>
In-Reply-To: <pull.1931.v2.git.1749202164.gitgitgadget@gmail.com>

On Fri, Jun 6, 2025, at 11:29, Johannes Schindelin via GitGitGadget wrote:
>        ## http.c ##
>      -@@ http.c: static CURL *get_curl_handle(void)
>      - 		die("curl_easy_init failed");
>      -
>      - 	if (!curl_ssl_verify) {
>      --		curl_easy_setopt(result, CURLOPT_SSL_VERIFYPEER, 0);
>      --		curl_easy_setopt(result, CURLOPT_SSL_VERIFYHOST, 0);
>      -+		curl_easy_setopt(result, CURLOPT_SSL_VERIFYPEER, 0l);
>      -+		curl_easy_setopt(result, CURLOPT_SSL_VERIFYHOST, 0l);

Maybe I don’t understand range-diffs enough but it looked like this was
using `0l` instead of `0L`.[1]  However the patches do use `<num>L` instead
of `<num>l` throughout.  Which I like

† 1: Or rather I don’t understand that this is showing `0l`