From b75763e07ef0f612eaf14b1f15a6d08983862d9b Mon Sep 17 00:00:00 2001
From: David Lawrence Ramsey <pooka109@gmail.com>
Date: Sun, 21 Nov 2004 17:45:25 +0000
Subject: [PATCH] update the given cvs commands in README.CVS so that they work
 again

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2113 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
---
 ChangeLog  |  1 +
 README.CVS | 13 ++++++++-----
 2 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 10f51166..257713ff 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -396,6 +396,7 @@ CVS code -
 	  v?snprintf(), and add minor formatting changes.
 	- Mention the requirement for groff in order to create html
 	  versions of the manpages. (DLR)
+	- Update the given cvs commands so that they work again. (DLR)
 - faq.html:
 	- Fixed inaccuracy: Pico compatibility mode was made the default
 	  in nano 1.1.99pre1, not 1.2.2. (DLR)
diff --git a/README.CVS b/README.CVS
index 9c4335e8..c0806692 100644
--- a/README.CVS
+++ b/README.CVS
@@ -19,19 +19,22 @@ packages:
 These should be available on your GNU mirror.
 
 To download the CVS tree, execute the following command:
-$ cvs -z3 -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/nano login
-and press enter at the password prompt.
+$ cvs -z3 -d:ext:anoncvs@savannah.gnu.org:/cvsroot/nano login
+and press Enter at the password prompt.
+
 Then, do
-$ cvs -z3 -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/nano checkout nano
+$ cvs -z3 -d:ext:anoncvs@savannah.gnu.org:/cvsroot/nano checkout nano
 and the nano tree will download.
-If you want to checkout the stable CVS branch, append -r nano_1_0_branch:
-$ cvs -z3 -d:pserver:anonymous@subversions.gnu.org:/cvsroot/nano checkout -r nano_1_0_branch nano
+
+If you want to download the stable CVS branch, add "-r nano_1_0_branch":
+$ cvs -z3 -d:ext:anoncvs@savannah.gnu.org:/cvsroot/nano checkout -r nano_1_0_branch nano
 
 Once you have the sources in the "nano" directory, cd into it, and
 execute the "autogen.sh" script in the top directory.  This will set up
 a configure script and Makefile.in, and you will be ready to compile
 with
 $ ./configure [--add-options-here] && make
+
 Once it's done compiling,
 $ make install
 (as root) should put the required files in their respective directories.
-- 
GitLab