Date: Mon, 26 Sep 2016 16:45:13 +0200 From: Gert Doering Message-ID: <20160926144513.GZ78279@...1296...> References: <1474109679-4982-1-git-send-email-chipitsine@...277...> <8a59c1b0-7bf5-47b8-68ed-ce36e4438c55@...515...> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QQOJ7tcb1Icu6LtL" Content-Disposition: inline In-Reply-To: Subject: Re: [Openvpn-devel] [PATCH] enable "--disable-crypto" build configuration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ???????? ?????????????? Cc: openvpn-devel --QQOJ7tcb1Icu6LtL Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, On Mon, Sep 26, 2016 at 01:26:24PM +0500, ???????? ?????????????? wrote: > it would be easiest, but it is not required. > as Steffan Karger wrote "Could you please include such descriptions in > future patches?" Well, a proper commit message *is* required. So, instead of us having do your work (of providing a proper commit message= ), and then complaining that this is taking a bit longer (because it's extra work) - what about "re-sending the patch with a proper commit message"=20 instead? I have a bunch of work to do, and "make me do more work and then complain that I'm slow doing it" is a very trusted way to get moved all the way=20 DOWN on my priority list. Like, "I might think about this next May". gert --=20 USENET is *not* the non-clickable part of WWW! //www.muc.de/~ge= rt/ Gert Doering - Munich, Germany gert@...1296... fax: +49-89-35655025 gert@...1297... --QQOJ7tcb1Icu6LtL Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQCVAwUBV+k0eakuBuNlUUl1AQIr+gQArrrEtlaCPv6rEFACnw6LWiwgCCMVnThy bwI8MrGQDfDPb5co4YP81hICn9e93IpFozcVDvZgSzbKKrMzuR1gxDDsiXeBNDkX AhW/frKRQYlnfsFGqBUukNOOORgJzUyPHrQ6ZdVEix/2MMORjX6E7MdRgHLLubzH IrvOLzXnltA= =f0Ev -----END PGP SIGNATURE----- --QQOJ7tcb1Icu6LtL--