Hang on a sec. Why would you think that you should close the PR if they don't respond? "standard responses" are great, but they are far too easy to just apply everywhere without looking at the problem. Just because a PR hasn't been updated in a while doesn't mean the submitter has to do anything.
This, for example, is a known problem caused by known things. On 28 May 1998 [EMAIL PROTECTED] wrote: > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > > > Synopsis: Buffering of script output is not switched off > > State-Changed-From-To: analyzed-feedback > State-Changed-By: coar > State-Changed-When: Thu May 28 12:34:22 PDT 1998 > State-Changed-Why: > [This is a standard response.] > This Apache problem report has not been updated recently. > Please reply to this message if you have any additional > information about this issue, or if you have answers to > any questions that have been posed to you. If there are > no outstanding questions, please consider this a request > to try to reproduce the problem with the latest software > release, if one has been made since last contact. If we > don't hear from you, this report will be closed. >
