-\versionid $Id: feedback.but,v 1.14 2003/09/23 10:05:06 jacob Exp $
+\versionid $Id: feedback.but,v 1.17 2004/03/31 12:50:17 simon Exp $
\A{feedback} Feedback and bug reporting
delayed and it may not be obvious which version was the latest at
the time you sent the message.
-\b Tell us what version of what OS you are running PuTTY on.
-(If you're running on Windows for Alpha, tell us, or we'll assume
-you're running on Intel as this is overwhelmingly the case.)
+\b PuTTY is a multi-platform application; tell us what version of what
+OS you are running PuTTY on. (If you're running on Unix, or Windows
+for Alpha, tell us, or we'll assume you're running on Windows for
+Intel as this is overwhelmingly the case.)
\b Tell us what protocol you are connecting with: SSH, Telnet,
Rlogin or Raw mode.
the request. (But see \k{feedback-feature-priority} if you want to
persuade us to give your particular feature higher priority.)
-\b Check the
+\b Check the Wishlist and
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{Change
Log} on the PuTTY website, and see if we have already added your
feature in the development snapshots. If it isn't clear, download
then \e{permission is already granted}. You don't have to mail us
and ask. Just go ahead and do it. We don't mind.
+(If you want to distribute PuTTY alongside your own application for
+use with that application, or if you want to distribute PuTTY within
+your own organisation, then we recommend you offer your own
+first-line technical support, to answer questions about the
+interaction of PuTTY with your environment. If your users mail us
+directly, we won't be able to tell them anything useful about your
+specific setup.)
+
If you want to use parts of the PuTTY source code in another
program, then it might be worth mailing us to talk about technical
details, but if all you want is to ask permission then you don't
projects / u / mdw / putty / blobdiff