Re: svn commit: r1833827 - /httpd/httpd/trunk/server/log.c

[Eric Covener]

> I looked at that a bit and the loop seemed pretty tight.  At some
> point I was looking to explicit reset ap_server_conf but then thought
> it was not necessary  -- maybe no hooks called between cleanups and
> re-assignment?

Thanks for the original followup on this one Bill -- It is actually a
big window due to EXEC_ON_READ http//svn.apache.org/r1835094

Re: svn commit: r1834671 - in /httpd/httpd/branches/2.4.x: CHANGES docs/manual/mod/mod_md.xml modules/md/md_crypt.c modules/md/md_json.c modules/md/md_version.h modules/md/mod_md.c modules/md/mod_md_c

[Stefan Eissing]

> Am 03.07.2018 um 13:54 schrieb Yann Ylavic :
> 
> On Tue, Jul 3, 2018 at 12:53 PM, Jim Jagielski  wrote:
>> 
>> 
>>> On Jul 2, 2018, at 1:40 PM, Christophe Jaillet 
>>>  wrote:
>>> 
>>> Le 02/07/2018 à 17:36, William A Rowe Jr a écrit :
 On Mon, Jul 2, 2018 at 8:25 AM, Stefan Eissing 
 mailto:stefan.eiss...@greenbytes.de>> wrote:
   I thought experimental == CTR, but if this is separate then I‘ll go
   through the votes. Just let me know what you prefer. I basically thought 
 the same thing, but it is clearly spelled out in STATUS.
 We aught to adjust this to reflect the eventual consensus;
  * Current exceptions for RTC for this branch:
. mod_proxy_http2
. mod_lua
. documentation
. non-Unix build
. non-Unix, single-platform code
>>> 
>>> I don't have a strong opinion about it, that's why I proposed to update 
>>> STATUS to add an exception for mod_md? (or maybe even for any module marked 
>>> as experimental?)
>>> 
>> 
>> +1 (for CTR for both mod_md *as well as* any module marked experimental)
> 
> +1

+1