Shout more loudly if we can't open a log file.

[PuTTY.git] / README

diff --git a/README b/README
index 72fc68c3a97009b3e109c5b8381159f60b0c595d..61f40b5f90fcebef36fba46fda9961b369571c7d 100644 (file)
--- 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