On 10/1/07, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:

> But I'm rather against breaking this in 2.2 to solve (what are, today)
> configuration quirks.  Let's get this right for 2.4 and call out the
> change very clearly in (our overlong) CHANGES?  I'm thinking of a new
> second-priority category after SECURITY:, e.g. CONFIG: or MUSTNOTE:
> so administrators who migrate aren't surprised.

Should be in this, rather sparse file:
http://httpd.apache.org/docs/trunk/new_features_2_4.html

Joshua.

Reply via email to