On 2/5/2010 7:05 PM, Graham Leggett wrote:
>
> Why does this not just use a simple pool cleanup on request end to
> restore the values, instead of all the song and dance to try and keep
> the previous value for restoration in the next request? Attaching it to
> a pool is fine, restoring it in the
On Sat, Feb 6, 2010 at 10:36 AM, Dan Poirier wrote:
> Thanks Jeff. Some thoughts and questions for all:
>
> * I'd think that all security fixes should be mentioned in CHANGES, with
> CVE number, regardless of other considerations. Otherwise people
> worry.
absolutely; you could list the forma
Thanks Jeff. Some thoughts and questions for all:
* I'd think that all security fixes should be mentioned in CHANGES, with
CVE number, regardless of other considerations. Otherwise people
worry.
* Should minor changes in the wording of a message be mentioned in
CHANGES? I'd guess not, ev
On Sat, Feb 6, 2010 at 8:59 AM, Dan Poirier wrote:
> Do we have any formal conventions (i.e. written down) on what kinds of
> changes require entries in CHANGES and what doesn't, and what
> information we include in CHANGES and svn log entries?
Here's a rough draft for people to throw stones at.
Do we have any formal conventions (i.e. written down) on what kinds of
changes require entries in CHANGES and what doesn't, and what
information we include in CHANGES and svn log entries?
The most logical place for something like that seems to be near the
bottom of http://httpd.apache.org/dev/guid
Hi,
Martin and myself are meeting sunday at 10:30 at the Mozilla room, where
we will meet up with Gerv from Mozilla. Please feel free to join.
The purpose is to discuss how to progress the delta-http protocol
support; more specifically the integration in Apache webserver through
mod-crcsync that
