Hi John,
Is there such a thing as a line-item veto? The patch did several
things, at least one of which -- fixing a bug in the documentation --
is ridiculous to veto. If someone would actually respond to the
I agree, but applying parts of patches is generally impossible and
undesirable. I agree that the documentation should get fixed.
issues I raised in my original message, I can submit a patch fixing
which ever issues people agree should be fixed. I don't think I'll
bother unless I get feedback, because I don't want to put any work
into it if it might get vetoed again.
I'm sorry for not responding to your earlier post, I have only so many
cycles. Generally you should separate out bug-fixes from changes to behavior
or enhancements. Genuine bug-fixes will almost always get applied. The
latter are more contentious. Indeed changing very visible user-behavior
midway through a release cycle will almost never happen even if it might be
the right thing to do.
Also please use unified diffs for patches (diff -u) they are much easier to
read. It was extremely difficult for me to tell what you had actually
changed. In general I think I am more lenient about applying patches than
Stephen is so please don't think that it is difficult to get changes in.
Thanks for your contribution, its appreciated.
andy