nano

commit 5cda85caaa99ed17e3bb4b2f60d9f01a594a1bd8
parent 5cb3f09a78e3940d2ac409e35a6e19bd5840fa5e
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Mon,  4 Apr 2016 18:46:21 -0400

README.GIT: update a few more points to match current tree

Diffstat:
M
README.GIT
 | 
12
++++++------

1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/README.GIT b/README.GIT
@@ -11,12 +11,12 @@ Prerequisites
 To successfully compile GNU nano from the git repo, you'll need the following
 packages:
 
-- autoconf (version >= 2.54)
+- autoconf (version >= 2.61)
 - automake (version >= 1.7)
 - gettext  (version >= 0.11.5)
 - groff    (version >= 1.12)
 - texinfo  (version >= 4.0)
-- subversion (aka svn)
+- git      (version >= 2.7.4)
 - glib 2.x (if your system doesn't have vsnprintf(), which the configure
   script will check for)
 - make, gcc and the normal development libraries (curses or slang, etc.)
@@ -29,9 +29,9 @@ to use UTF-8.
 Download the source
 -------------------
 
-To obtain the current nano development code (called 'trunk'), use the
-following command.  It will create a copy of the files in a subdirectory
-of your current working directory called 'nano':
+To obtain the current nano development code (called 'master', or sometimes
+'trunk'), use the following command.  It will create a copy of the files in
+a subdirectory of your current working directory called 'nano':
 
     $ git clone git://git.savannah.gnu.org/nano.git nano
 
@@ -63,7 +63,7 @@ From the nano source directory, build the code with:
 
     $ make
 
-Then, once it's done compiling, run
+Then, once it's done compiling, run:
 
     $ make install