Re: Votes on current patches

[Randy Terbush <ra...@zyzzyva.com>]

I'll mirror my votes from RST's.  All patches applied and tested on
SunOS 4.1.3 and NetBSD-current. The server is installed and running
on all of my webservers.

Regarding 04a: I agree that this could be an interesting feature.
Perhaps we can implement it in a way that will not cause problems for
robots as well...


> +1 01_http_config.0.8.14.patch
> +1 02_DBMGroupCoreFix.0.8.14.patch
> -1 03_XBITHACK_restrict.0.8.14.patch --- withdrawn [no patch present]
> +1 04a_ExtraPath.0.8.14.patch [after Ben's correction]
> +1 05_NoKill.0.8.14.patch
> +1 06_SCODocFix.0.8.14.patch
> +1 07_SocketMemLeak.0.8.14.patch
> +1 08_license.0.8.14.patch
> +1 09_HP_comment.0.8.14.patch
> +1 10_mutual-failure.0.8.14.patch
> +1 11_fd_removal.0.8.14.patch
> +1 12_del_max_security.0.8.14.patch
> +1 13_error_fd.0.8.14.patch
> +1 14_rlimit.0.8.14.patch
> +1 15_urlchars.0.8.14.patch
> +1 16_alias.0.8.14.patch
> -1 17_const.0.8.14.patch --- As I've said before, I feel cleanups of this
>       sort are inappropriate at this point in the release cycle.  
> +1 18_geteuid.apache_0.8.14.patch
> +1 19_redir.0.8.14.patch
> +1 20_score.0.8.14.patch
> +1 21.escape.0.8.14.patch
> +1 22.spawn.0.8.14.patch
> -1 23.mmap.0.8.14.patch --- Again, I don't feel this sort of thing is
>       appropriate at this point in the release cycle; it changes a
>       whole lot of code, and poses a substantial risk of causing more
>       problems than it cures.
> +1 24_imap.0.8.14.patch --- Two small changes, both fixing clear bugs.
> -1 25_startserver.0.8.14.patch --- See Andrew's comments.