~mdw
/
sgt
/
putty
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Oops. Fix a bug in my `keyfile-diagnostic' work which caused SSH-2 key loading
[sgt/putty]
/
doc
/
feedback.but
diff --git
a/doc/feedback.but
b/doc/feedback.but
index
0f1d0f3
..
9c34ae3
100644
(file)
--- a/
doc/feedback.but
+++ b/
doc/feedback.but
@@
-1,4
+1,4
@@
-\versionid $Id: feedback.but,v 1.
8 2002/08/12 14:08:55 simo
n Exp $
+\versionid $Id: feedback.but,v 1.
13 2003/06/06 18:16:52 be
n Exp $
\A{feedback} Feedback and bug reporting
\A{feedback} Feedback and bug reporting
@@
-34,6
+34,10
@@
you can trust the people on the list to respect that confidence.
Also, the archives aren't publicly available, so you shouldn't be
letting yourself in for any spam by sending us mail.
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
\S{feedback-largefiles} Sending large attachments
Since the PuTTY contact address is a mailing list, e-mails larger
@@
-62,7
+66,9
@@
problem. Please don't do this without checking with us first - we
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
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}
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}
@@
-88,7
+94,7
@@
If you think you have found a bug in PuTTY, your first steps should
be:
\b Check the
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
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
@@
-183,7
+189,7
@@
If you want to request a new feature in PuTTY, the very first things
you should do are:
\b Check the
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
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
@@
-235,7
+241,8
@@
on the Wishlist, or we might think you haven't even \e{read} the
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
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
\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
@@
-274,6
+281,11
@@
a different SSH client and see if it works with that. Please do not
report it as a PuTTY bug unless you are really sure it \e{is} a bug
in PuTTY.
report it as a PuTTY bug unless you are really sure it \e{is} a bug
in PuTTY.
+\b If someone else installed PuTTY for you, or you're using PuTTY on
+someone else's computer, try asking them for help first. They're more
+likely to understand how they installed it and what they expected you
+to use it for than we are.
+
\b If you have successfully made a connection to your server and now
need to know what to type at the server's command prompt, or other
details of how to use the server-end software, talk to your server's
\b If you have successfully made a connection to your server and now
need to know what to type at the server's command prompt, or other
details of how to use the server-end software, talk to your server's