On 07/02/2017 15:03, David Sommerseth wrote:
> On 07/02/17 11:09, Samuli Seppänen wrote:
>> Actually, that was just the line length for _code_, not for commit
>> messages. So the only indirect guideline for Git commit message line
>> length was
>
> Correct.
>
>> "The maximum length of the line
2017-02-07 18:11 GMT+05:00 David Sommerseth <
open...@sf.lists.topphemmelig.net>:
> On 07/02/17 11:23, Илья Шипицин wrote:
> > as for compliance check, it will always annoy people if it is something
> > written somewhere. people will forget to have a look at it.
> > can we involve something like
On 07/02/17 11:23, Илья Шипицин wrote:
> as for compliance check, it will always annoy people if it is something
> written somewhere. people will forget to have a look at it.
> can we involve something like that
>
> https://github.com/openresty/lua-nginx-module/blob/master/.travis.yml#L61-L62
> ?
On 07/02/17 11:09, Samuli Seppänen wrote:
> Actually, that was just the line length for _code_, not for commit
> messages. So the only indirect guideline for Git commit message line
> length was
Correct.
> "The maximum length of the line differs between projects, it's usually
> somewhere
Hello,
Good question. For the test, I looked how it was done in other parts
of ssl_openssl.c, like around line 1518:
https://github.com/OpenVPN/openvpn/blob/master/src/openvpn/ssl_openssl.c#L1518-L1522
and did the same.
And as said by Gert, crypto_msg() solve it.
I'm sorry, in my first message,
Hi,
On Tue, Feb 07, 2017 at 12:09:45PM +0200, Samuli Seppänen wrote:
> The "seven rules" URL David linked to says the following:
>
> * Limit the subject line to 50 characters
> * Wrap the body at 72 characters
>
> I can't recall us ever agreeing to such limits.
>
> Let's agree on what we want
2017-02-07 15:09 GMT+05:00 Samuli Seppänen :
> On 07/02/2017 11:06, Samuli Seppänen wrote:
>
>> On 06/02/2017 12:44, David Sommerseth wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> I have ACKed and applied this, just to get this one resolved. But I am
On 07/02/2017 11:06, Samuli Seppänen wrote:
> On 06/02/2017 12:44, David Sommerseth wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> I have ACKed and applied this, just to get this one resolved. But I am very
>> disappointed that you have yet again completely ignored the
On 06/02/2017 12:44, David Sommerseth wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have ACKed and applied this, just to get this one resolved. But I am very
> disappointed that you have yet again completely ignored the guidelines
> described in the URL[1] already provided to you
2017-02-07 9:14 GMT+05:00 Antonio Quartulli :
> On Mon, Feb 06, 2017 at 08:18:01PM +0100, Olivier W wrote:
> > Should be compatible with all versions of OpenSSL and LibreSSL.
> > Similar to what is done in curl:
> >
Hi,
On Tue, Feb 07, 2017 at 12:14:51PM +0800, Antonio Quartulli wrote:
> > +if (!ssl)
> > +{
> > +crypto_msg(M_FATAL, "SSL_new failed");
> > +}
> > +pkey = SSL_get_privatekey(ssl);
> > +SSL_free(ssl);
>
> I have a question (sorry if I couldn't
11 matches
Mail list logo