-\versionid $Id: feedback.but,v 1.6 2002/08/05 10:35:23 simon Exp $
+\versionid $Id: feedback.but,v 1.12 2003/01/24 14:12:31 jacob Exp $
\A{feedback} Feedback and bug reporting
Also, the archives aren't publicly available, so you shouldn't be
letting yourself in for any spam by sending us mail.
+Please use a meaningful subject line on your message. We get a lot of
+mail, and it's hard to find the message we're looking for if they all
+have subject lines like \q{PuTTY bug}.
+
\S{feedback-largefiles} Sending large attachments
Since the PuTTY contact address is a mailing list, e-mails larger
almost never actually need the information in the screen shot.
Sending a screen shot of an error box is almost certainly
unnecessary when you could just tell us in plain text what the error
-was. Sending a full-screen shot is \e{occasionally} useful, but it's
+was. (On some versions of Windows, pressing Ctrl-C when the error
+box is displayed will copy the text of the message to the clipboard.)
+Sending a full-screen shot is \e{occasionally} useful, but it's
probably still wise to check whether we need it before sending it.
If you \e{must} mail a screen shot, don't send it as a \cw{.BMP}
than other image formats such as PNG, TIFF and GIF. Convert the file
to a properly compressed image format before sending it.
-Please don't mail us executables, at all. For security reasons, it
-would be really unwise of us to run executables we receive from
-unknown people by e-mail, so there's no point sending them to us. At
-some point, indeed, we hope to block all incoming e-mail containing
-executables, as a defence against the vast numbers of e-mail viruses
-we receive every day.
+Please don't mail us executables, at all. Our mail server blocks all
+incoming e-mail containing executables, as a defence against the
+vast numbers of e-mail viruses we receive every day. If you mail us
+an executable, it will just bounce.
If you have made a tiny modification to the PuTTY code, please send
us a \e{patch} to the source code if possible, rather than sending
be:
\b Check the
-\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist.html}{Wishlist
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist
page} on the PuTTY website, and see if we already know about the
problem. If we do, it is almost certainly not necessary to mail us
about it, unless you think you have extra information that might be
you should do are:
\b Check the
-\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist.html}{Wishlist
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist
page} on the PuTTY website, and see if your feature is already on
the list. If it is, it probably won't achieve very much to repeat
the request. (But see \k{feedback-feature-priority} if you want to
Wishlist). This probably won't have very \e{much} effect; if a huge
number of people vote for something then it may make a difference,
but one or two extra votes for a particular feature are unlikely to
-change our priority list immediately. Also, don't expect a reply.
+change our priority list immediately. Offering a new and compelling
+justification might help. Also, don't expect a reply.
\b Offer us money if we do the work sooner rather than later. This
sometimes works, but not always. The PuTTY team all have full-time
If you want to report a problem with our web site, check that you're
looking at our \e{real} web site and not a mirror. The real web site
-is at \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}; if
-that's not where you're reading this, then don't report the problem
-to us until you've checked that it's really a problem with the main
-site. If it's only a problem with the mirror, you should try to
-contact the administrator of that mirror site first, and only
+is at
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}\c{http://www.chiark.greenend.org.uk/~sgtatham/putty/};
+if that's not where you're reading this, then don't report the
+problem to us until you've checked that it's really a problem with
+the main site. If it's only a problem with the mirror, you should
+try to contact the administrator of that mirror site first, and only
contact us if that doesn't solve the problem (in case we need to
remove the mirror from our list).