putty-source/doc/vids.but

\# Invoke the versionid macros defined in all the other manual
\# chapter files.

\versionidblurb

\versionidintro

\versionidgs

\versionidusing

\versionidconfig

\versionidpscp

\versionidpsftp

\versionidplink

\versionidpubkey

\versionidpageant

\versioniderrors

\versionidfaq

\versionidfeedback

\versionidlicence

\versionidudp
Now we use Subversion, it seems excessive to have an individual $Id$ line for every single .but file at the bottom of each page of the HTML PuTTY docs. However, we can't _always_ replace that with a single SVN revision, because there isn't always one available (SVN still allows mixed working copies in which some files are deliberately checked out against a different revision). Hence, here's a mechanism for doing better. It uses `svnversion .' to determine _whether_ a single revision number adequately describes the current directory, and replaces all the version IDs with that if so. If it can't do that, it uses the version IDs as before. Also, this allows an explicit version string to be passed on the make command line which will override _both_ these possibilities, so that release documentation can be clearly labelled with the release version number. [originally from svn r4804] 2004-11-17 18:16:59 +00:00			`\# Invoke the versionid macros defined in all the other manual`
			`\# chapter files.`

			`\versionidblurb`

			`\versionidintro`

			`\versionidgs`

			`\versionidusing`

			`\versionidconfig`

			`\versionidpscp`

			`\versionidpsftp`

			`\versionidplink`

			`\versionidpubkey`

			`\versionidpageant`

			`\versioniderrors`

			`\versionidfaq`

			`\versionidfeedback`

			`\versionidlicence`
Add an extra appendix to the manual containing PuTTY's (hitherto) unwritten design principles, so would-be contributors won't have to either read our minds or pay _very_ close attention to the code. [originally from svn r4815] 2004-11-18 15:16:18 +00:00
			`\versionidudp`