summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim Meyering <meyering@redhat.com>2008-01-23 00:18:24 +0100
committerJim Meyering <meyering@redhat.com>2008-01-23 00:18:24 +0100
commit3b9b0c5c161e4df0d0b64128241c2d924f70858b (patch)
treec1b1c84e2d56633ed11fc1077ef8335c6e009991
parent5983242eef053a2edc6178d5bb58c5539cf986d6 (diff)
downloadcoreutils-3b9b0c5c161e4df0d0b64128241c2d924f70858b.tar.xz
* README: Remove/convert a few stray mentions of CVS.
-rw-r--r--ChangeLog4
-rw-r--r--README14
2 files changed, 10 insertions, 8 deletions
diff --git a/ChangeLog b/ChangeLog
index c586ef89d..79ec5efd4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2008-01-23 Jim Meyering <meyering@redhat.com>
+
+ * README: Remove/convert a few stray mentions of CVS.
+
2008-01-22 Jim Meyering <meyering@redhat.com>
Require automake-1.10.1, for its support of dist-lzma.
diff --git a/README b/README
index 49140524a..7a608f41c 100644
--- a/README
+++ b/README
@@ -18,10 +18,9 @@ The programs that can be built with this package are:
See the file NEWS for a list of major changes in the current release.
-If you obtained this file as part of a "cvs checkout" or "git clone",
-then see the README-hacking file. If this file came to you as part of a
-tar archive, then see the file INSTALL for compilation and installation
-instructions.
+If you obtained this file as part of a "git clone", then see the
+README-hacking file. If this file came to you as part of a tar archive,
+then see the file INSTALL for compilation and installation instructions.
These programs are intended to conform to POSIX (with BSD and other
extensions), like the rest of the GNU system. By default they conform
@@ -185,14 +184,13 @@ If you sent a complete patch and, after a couple weeks you haven't
received any acknowledgement, please ping us. A complete patch includes
a well-written ChangeLog entry, unified (diff -u format) diffs relative
to the most recent test release (or, better, relative to the latest
-sources in the CVS repository), an explanation for why the patch is
+sources in the public repository), an explanation for why the patch is
necessary or useful, and if at all possible, enough information to
reproduce whatever problem prompted it. Plus, you'll earn lots of
karma if you include a test case to exercise any bug(s) you fix.
-Instructions for checking out the latest source via CVS are here:
-
- http://savannah.gnu.org/cvs/?group=coreutils
+Here are instructions for checking out the latest development sources:
+ http://savannah.gnu.org/git/?group=coreutils
If your patch adds a new feature, please try to get some sort of consensus
that it is a worthwhile change. One way to do that is to send mail to