httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@gmail.com>
Subject Re: svn commit: r159356 - httpd/httpd/trunk/CHANGES
Date Tue, 29 Mar 2005 11:12:41 GMT
On Tue, 29 Mar 2005 00:50:45 -0800, Paul Querna <chip@force-elite.com> wrote:
> trawick@apache.org wrote:
> > Author: trawick
> > Date: Tue Mar 29 00:44:53 2005
> > New Revision: 159356
> >
> > URL: http://svn.apache.org/viewcvs?view=rev&rev=159356
> > Log:
> > sync with 2.0.54-dev
> >
> > Modified:
> >     httpd/httpd/trunk/CHANGES
> >
> > Modified: httpd/httpd/trunk/CHANGES
> > URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/CHANGES?view=diff&r1=159355&r2=159356
> > ==============================================================================
> > --- httpd/httpd/trunk/CHANGES (original)
> > +++ httpd/httpd/trunk/CHANGES Tue Mar 29 00:44:53 2005
> > @@ -57,10 +57,6 @@
> >    *) Only recompile buildmark.c when we have to relink httpd.
> >       [Justin Erenkrantz]
> >
> > -  *) Remove formatting characters from ap_log_error() calls.  These
> > -     were escaped as fallout from CAN-2003-0020.
> > -     [Eric Covener <ecovener gmail.com>]
> > -
> >    *) mod_cache: Fix up handling of revalidated responses.
> >       [Justin Erenkrantz]
> >
> > @@ -630,6 +626,10 @@
> >     Apache 2.0.xx tree as documented, and except as noted, below.]
> >
> >  Changes with Apache 2.0.54
> > +
> > +  *) Remove formatting characters from ap_log_error() calls.  These
> > +     were escaped as fallout from CAN-2003-0020.
> > +     [Eric Covener <ecovener gmail.com>]
> >
> >    *) htdigest: Fix permissions of created files.  PR 33765.  [Joe Orton]
> 
> I don't think we should remove entries from the 2.1.x Changes anymore.
> 
> Since there are real changes between patch releases of 2.1.x, removing
> this changes entry means that someone upgrading from 2.1.2 would not see
> this one listed.
> 
> I think from now on, items should be listed in both 2.1.x and 2.0.x.

I had assumed we would do this when 2.2 became GA...  I have no strong
opinion on exactly when it happens.

> On a different matter, should truncating the CHANGES be considered for
> trunk?  Eg, only show changes since 2.0 or even 2.1.0? (At a minimum,
> cut out all the old old old old changes in 1.3..)

shrug... that's the declaration that many of those old contributions
are part of even the latest level of Apache...

Mime
View raw message