From 09111ea9c27c5f0c2d66866294f3ad9bfc08db9f Mon Sep 17 00:00:00 2001 From: Ben Harris Date: Sat, 1 Nov 2014 17:17:57 +0000 Subject: [PATCH] Update documentation to refer to Git rather than Subversion. --- README | 6 +++--- doc/faq.but | 2 +- doc/pgpkeys.but | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/README b/README index 72fc68c3..61f40b5f 100644 --- a/README +++ b/README @@ -3,7 +3,7 @@ and Unix Telnet and SSH client. If you want to rebuild PuTTY from source, we provide a variety of Makefiles and equivalents. (If you have fetched the source from -Subversion, you'll have to generate the Makefiles yourself -- see +Git, you'll have to generate the Makefiles yourself -- see below.) There are various compile-time directives that you can use to @@ -103,7 +103,7 @@ For building on Unix: - The Unix Makefiles have an `install' target. Note that by default it tries to install `man' pages; if you have fetched the source via - Subversion then you will need to have built these using Halibut + Git then you will need to have built these using Halibut first - see below. - It's also possible to build the Windows version of PuTTY to run @@ -119,7 +119,7 @@ corrections to the actual Makefiles, Makefile.am or Makefile.in. The Unix `configure' script and its various requirements are generated by the shell script `mkauto.sh', which requires GNU Autoconf, GNU -Automake, and Gtk; if you've got the source from Subversion rather +Automake, and Gtk; if you've got the source from Git rather than using one of our source snapshots, you'll need to run this yourself. The input file to Automake is generated by mkfiles.pl along with all the rest of the makefiles, so you will need to run mkfiles.pl diff --git a/doc/faq.but b/doc/faq.but index 25a849b7..8bf1f32d 100644 --- a/doc/faq.but +++ b/doc/faq.but @@ -1187,7 +1187,7 @@ Partly, because we don't want to move the web site location (see Also, security reasons. PuTTY is a security product, and as such it is particularly important to guard the code and the web site against unauthorised modifications which might introduce subtle security -flaws. Therefore, we prefer that the Subversion repository, web site and +flaws. Therefore, we prefer that the Git repository, web site and FTP site remain where they are, under the direct control of system administrators we know and trust personally, rather than being run by a large organisation full of people we've never met and which is diff --git a/doc/pgpkeys.but b/doc/pgpkeys.but index b0331fc3..e6f25c6b 100644 --- a/doc/pgpkeys.but +++ b/doc/pgpkeys.but @@ -71,7 +71,7 @@ human intervention, so nobody would be able to type a passphrase. The actual snapshots are built on a team member's home Windows box. The keys themselves are stored on an independently run Unix box -(the same one that hosts our Subversion repository). After +(the same one that hosts our Git repository). After being built, the binaries are uploaded to this Unix box and then signed automatically. -- 2.45.2