On 7/10/2011 5:34 PM, Roy T. Fielding wrote: > Regardless of anyone else's opinion, the addition or deletion of a > new API to our product is a technical change that can be vetoed. > Likewise, the API being an incomplete abstraction that isn't > needed in httpd is a valid technical reason to veto it even if > it had once been in apr-util. > > Other than the convoluted history of this particular argument, > I don't see any reason for further frustration. Revert the commit.
I believe svn rm ... svn cp -r of the origin files to jump across the rejected patches is the most efficient and least confusing revert? The only complexity is to ensure configure.in/ or other peripheral changes are not lost. I have the cycles do this Tuesday, if not Monday.
