On Thu, Oct 22, 2020 at 08:41:35PM +0200, William Lallemand wrote: > On Thu, Oct 22, 2020 at 10:20:12PM +0500, Илья Шипицин wrote: > > can we backport > > http://git.haproxy.org/?p=haproxy.git;a=commit;h=b3201a3e077198b3f75ebe8661aa45589b811552 > > to 2.1 as well ? it was not scheduled, but it is required to fix BoringSSL > > builds > > > > BoringSSL does not have any maintenance branches and they encourage to > have the boringSSL code shipped with the programs that use it. > > That's why we shouldn't spend much time doing boringSSL maintenance in > older branches, it does not make much sens to me. Or we will spend our > time fixing boringSSL build for old versions each time they change their > API. That's not how a stable branch is supposed to work. > > Since people using boringSSL does not use a boringSSL release, I don't > see why they would need a haproxy release :-) >
I just backported both patches as the conflicts were quite simple to resolve. -- William Lallemand
