-\versionid $Id: feedback.but,v 1.8 2002/08/12 14:08:55 simon Exp $
+\versionid $Id: feedback.but,v 1.11 2003/01/17 13:32:51 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}
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