Thiago Farina writes:
> On Mon, Mar 31, 2014 at 5:50 PM, Junio C Hamano wrote:
>> Thiago Farina writes:
>>
>>> In imap-send.c:socket_perror() we pass |func| as a parameter, which I
>>> think it is the name of the function that "called" socket_perror, or
>>> the name of the function which genera
On Mon, Mar 31, 2014 at 5:50 PM, Junio C Hamano wrote:
> Thiago Farina writes:
>
>> In imap-send.c:socket_perror() we pass |func| as a parameter, which I
>> think it is the name of the function that "called" socket_perror, or
>> the name of the function which generated an error.
>>
>> But at line
Thiago Farina writes:
> In imap-send.c:socket_perror() we pass |func| as a parameter, which I
> think it is the name of the function that "called" socket_perror, or
> the name of the function which generated an error.
>
> But at line 184 and 187 it always assume it was SSL_connect.
>
> Should we
Hi,
In imap-send.c:socket_perror() we pass |func| as a parameter, which I
think it is the name of the function that "called" socket_perror, or
the name of the function which generated an error.
But at line 184 and 187 it always assume it was SSL_connect.
Should we instead call perror() and ssl_s
4 matches
Mail list logo