There are three more, so we have 7 places for mod_ssl: patches trunk-md 2.4.x-mod_md branch 2.4.x git v5 patch trunk 2.5.0-alpha
Please be clear what is what and which are obsolete ? It is a mess for me. > Op 6 jan. 2018 om 12:17 heeft Steffen <i...@apachelounge.com> het volgende > geschreven: > > Sorry overlooked it: the change is included in 2.4.x-mod_md and not in 2.4.x. > mod_ssl in 2.4.x-mod_md branch does not build out of the box: > > in ssl_engine_init.c have to set #define MOD_MD_BACKPORTED 1 > > >> On 6-1-2018 08:07, Steffen wrote: >> Not sure: Looks that now we loose the latest change yesterday from icing in >> 2.4.x-mod_md branch ? >> >> >> ------------ Begin Message ------------ >> Group: gmane.comp.apache.devel >> MsgID: <CAKQ1sVOgrZVz5ErCiCrB8v29B=dwYiysRXMa1P7+aT65=cx...@mail.gmail.com> >> >> Hi Steffen, >> >>> On Fri, Jan 5, 2018 at 10:26 PM, Steffen <i...@apachelounge.com> wrote: >>> What is the one we have to test for next 2.4.30, special mod_md 1.1.8 >> I have just synchonized the 2.4.x-mod_md branch with 2.4.x (resolving >> only a tiny conflict in a comment). >> So they should be exactly the same (mod_ssl included), except for the >> pure mod_md changes, thus you should use the 2.4.x-mod_md branch I >> guess. >> >> Attached is the diff between the two branches' mod_ssl (svn diff -x-p >> ^/httpd/httpd/branches/2.4.x/modules/ssl >> ^/httpd/httpd/branches/2.4.x-mod_md/modules/ssl). >> Regarding the Windows build (.win, .mak, .dsp, ..., including the ones >> at the root directory), the 2.4.x-mod_md branch seems also to be up to >> date. >> >> Regards, >> Yann. >> >> >> >> >> ------------- End Message ------------- >> >> >
