+1. They can even make their configuration "future proof" today by setting the 2.4 default behaviour explicitly.
Regards Rüdiger > -----Original Message----- > From: Jim Jagielski [mailto:[email protected]] > Sent: Dienstag, 30. Juni 2015 12:25 > To: [email protected] > Cc: [email protected] > Subject: Re: svn commit: r1688331 - > /httpd/httpd/trunk/modules/filters/mod_substitute.c > > My pref is that we create one single directive which controls > this. With 2.4 the default is the "old" (incorrect) merge and > with trunk it is the new (correct) merge. That way those > upgrading from 2.4 -> 2.6/3.0 will only need to worry about > a directive default change.
