> Bill Stoddard wrote: > > > I am a strong +1 in favor of making this a subproject and probably rolling it into >a post > > 2.0 release. The presence of mod_gz in the core now -will- impact folks who are working on > > stabilizing the server. > > What about putting it in the experimental directory? This way it's > available for the adventurous, but will not impact on the people who are > after stability. > That works for me as long as we do not attempt to integrate it into the build environment until after 2.0 goes out. Bill
- Re: cvs commit: httpd-2.0 STATUS Joshua Slive
- Re: cvs commit: httpd-2.0 STATUS Jeff Trawick
- Re: cvs commit: httpd-2.0 STATUS Rodent of Unusual Size
- Re: cvs commit: httpd-2.0 STATUS Ryan Bloom
- Re: cvs commit: httpd-2.0 STATUS Graham Leggett
- Re: cvs commit: httpd-2.0 STATUS Ryan Bloom
- Re: cvs commit: httpd-2.0 STATUS Graham Leggett
- Re: cvs commit: httpd-2.0 STATUS Bill Stoddard
- Re: cvs commit: httpd-2.0 STATUS Graham Leggett
- Re: cvs commit: httpd-2.0 STATUS Bill Stoddard
- Re: cvs commit: httpd-2.0 STATUS Ryan Bloom
- Re: cvs commit: httpd-2.0 STATUS Jim Jagielski
- Re: cvs commit: httpd-2.0 STATUS Justin Erenkrantz
- Re: cvs commit: httpd-2.0 STATUS Ryan Bloom
- Re: cvs commit: httpd-2.0 STATUS Rodent of Unusual Size
- Re: cvs commit: httpd-2.0 STATUS Cliff Woolley
- Re: cvs commit: httpd-2.0 STATUS Justin Erenkrantz
- Re: cvs commit: httpd-2.0 STATUS Rodent of Unusual Size
- Re: cvs commit: httpd-2.0 STATUS Cliff Woolley
- Re: cvs commit: httpd-2.0 STATUS William A. Rowe, Jr.
