Re: [PATCH v2 0/4] curl: pass long values where expected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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`





[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux