It seems to me (catching up on my vacation Email) that the issues can be resolved by simply reverting the patches on trunk while maintaining development on the async branch. Certainly one reason for such branches is to allow for sideline development without affecting the main development branch with changes that are unproven yet (or not so self-contained as to allow inline development). -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "If you can dodge a wrench, you can dodge a ball."
- Re: svn commit: r360461 - in /httpd/httpd/trunk: CHAN... Brian Pane
- Re: svn commit: r360461 - in /httpd/httpd/trunk:... Roy T. Fielding
- Re: svn commit: r360461 - in /httpd/httpd/tr... Brian Pane
- Re: svn commit: r360461 - in /httpd/httpd/tr... Roy T. Fielding
- Re: svn commit: r360461 - in /httpd/http... William A. Rowe, Jr.
- Re: svn commit: r360461 - in /httpd/... Roy T. Fielding
- Re: svn commit: r360461 - in /h... William A. Rowe, Jr.
- Re: svn commit: r360461 - in /httpd/httpd/trunk:... Jim Jagielski
- Re: svn commit: r360461 - in /httpd/httpd/trunk:... Justin Erenkrantz
- Re: svn commit: r360461 - in /httpd/httpd/tr... Brian Pane
- Re: svn commit: r360461 - in /httpd/http... Justin Erenkrantz
- Re: svn commit: r360461 - in /httpd/... Brian Pane
- async reads - request for comme... Brian Pane