Hi Ilya,
my 2-meta-cents here: when sending multiple versions of the same patch to the
mailing list, I'd recommend to change the subject to "[PATCHvX]" where X is
the patch version.
This way it is easier to identify which patch comes before and which after.
Not sure what the maintainers think ab
On Sun, Jan 29, 2017 at 1:58 AM, Ilya Shipitsin
wrote:
> MBEDTLS_VERSION, OPENSSL_VERSION were defined twice - in both
> .travis.yml and .travis/build-deps.sh files, the last one
> defined OPENSSL_VERSION via nonexistent OPENSSL_VERION
> variable, which lead us to use openssl-1.0.1 instead of
>
Hi,
On Sun, Jan 29, 2017 at 11:43:04PM +0800, Antonio Quartulli wrote:
> Not sure what the maintainers think about this, but I stumbled on the wrong
> version a couple of times today before realizing that the newer was another
> one.
Either "[PATCH v2]" or at least mention "v2: " in the commit
m
On 29/01/17 19:13, Gert Doering wrote:
>
>> Git can do this for you by specifying "-v X" (i.e. -v 2" to the git
>> format-patch
>> command.
>
> I've learned something new today :-) (but I shouldn't be surprised: git
> is known to do everything to ease lazy committers' work :-) )
Weee! I realize
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your patch has been applied to the following branches
commit 208c03ea145ed89083c43267733487c99a805069 (master)
commit 31af45abfad7e3f0fbafc82b2daef3400a93359c (release/2.4)
Author: Ilya Shipitsin
Date: Sun Jan 29 11:58:11 2017 +0500
Resolve
can we merge it ?
@mattock ?
2017-01-21 13:47 GMT+05:00 Илья Шипицин :
>
>
> 2017-01-21 0:24 GMT+05:00 David Sommerseth topphemmelig.net>:
>
>> On 13/01/17 10:05, Samuli Seppänen wrote:
>> > Il 13/01/2017 10:50, Ilya Shipitsin ha scritto:
>> >> ---
>> >> .github/PULL_REQUEST_TEMPLATE.md | 8 +++
