nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-26 01:32:25 +00:00
Code Issues Projects Releases Wiki Activity

Explicitly add linking to our website to the "asking permission for things"

Browse Source 
section.
Replace the FAQ text with a summary + link to feedback.but.

[originally from svn r6613]
This commit is contained in:
Jacob Nevins 2006-03-15 14:31:39 +00:00
parent 0e621f9660
commit 5d13c986b1
2 changed files with 11 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/faq.but
View File

@ -1210,18 +1210,10 @@ feel perfectly free not to donate. We don't mind.
\S{faq-permission}{Question} Can I have permission to put PuTTY on a \S{faq-permission}{Question} Can I have permission to put PuTTY on a
cover disk / distribute it with other software / etc? cover disk / distribute it with other software / etc?
Yes. You need not bother asking us explicitly for permission. You Yes. For most things, you need not bother asking us explicitly for
already have permission. Redistribution of the unmodified PuTTY permission; our licence already grants you permission.
binary in this way is entirely permitted by our licence (see
\k{licence}), and you are welcome to do it as much as you like.
If you are distributing PuTTY within your own organisation, or for See \k{feedback-permission} for more details.
use with your own product, then we recommend (but do not insist)
that you offer your own first-line technical support, to answer
questions directly relating to the interaction of PuTTY with your
particular environment. If your users mail us directly, we won't be
able to give them very much help about things specific to your own
setup.
\S{faq-indemnity}{Question} Can you sign an agreement indemnifying \S{faq-indemnity}{Question} Can you sign an agreement indemnifying
us against security problems in PuTTY? us against security problems in PuTTY?

13
doc/feedback.but
View File

@ -356,17 +356,20 @@ and ask. Just go ahead and do it. We don't mind.
(If you want to distribute PuTTY alongside your own application for (If you want to distribute PuTTY alongside your own application for
use with that application, or if you want to distribute PuTTY within use with that application, or if you want to distribute PuTTY within
your own organisation, then we recommend you offer your own your own organisation, then we recommend, but do not insist, that
first-line technical support, to answer questions about the you offer your own first-line technical support, to answer questions
interaction of PuTTY with your environment. If your users mail us about the interaction of PuTTY with your environment. If your users
directly, we won't be able to tell them anything useful about your mail us directly, we won't be able to tell them anything useful about
specific setup.) your specific setup.)
If you want to use parts of the PuTTY source code in another 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 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 details, but if all you want is to ask permission then you don't
need to bother. You already have permission. need to bother. You already have permission.
If you just want to link to our web site, just go ahead. (It's not
clear that we \e{could} stop you doing this, even if we wanted to!)
\H{feedback-mirrors} Mirroring the PuTTY web site \H{feedback-mirrors} Mirroring the PuTTY web site
\#{This paragraph also in putty-website/mirrors.html} \#{This paragraph also in putty-website/mirrors.html}