References: <1511554982-875-1-git-send-email-jim@...2322...> <14a28e53-a002-8c03-69e1-44af1529f080@...2181...> <18ff01d36c48$e396eac0$aac4c040$@carroll.com> <57908e74-0039-0021-26f1-0ca2df32d53c@...2080...> <17c701d37020$f0ef10e0$d2cd32a0$@carroll.com> From: Steffan Karger Message-ID: <93aac1a6-1a5d-acfa-1465-0462b3f599a6@...1856...> Date: Fri, 8 Dec 2017 13:40:34 +0100 MIME-Version: 1.0 In-Reply-To: <17c701d37020$f0ef10e0$d2cd32a0$@carroll.com> Content-Language: en-GB Subject: Re: [Openvpn-devel] [PATCH] Added OpenSSL FIPS 2.0 support to OpenVPN List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: openvpn-devel@lists.sourceforge.net Hi, On 08-12-17 13:34, Jim Carroll wrote: > I'm curious about the openvpn-devel process related to patch acceptance. Does > the fact that the conversation has ended mean the patch is scheduled to be > added -- or does it instead mean there is no interest and the patch is being > denied? It means no one had time to look at it yet. Most of the developers process patches in their spare cycles, and those can be scarce :( In this case: it's on my todo list, but so are many other things. We'll get to it at some point, but I can't tell you when unfortunately. -Steffan