Mention the CVS repository.

Encourage addition of test cases.

diff --git a/README b/README
index 7bee8e1678943b231fc15f24660b74cae464f844..77ac5afd3396bb21dc4b6375cf9ced319738014a 100644 (file)
--- a/README
+++ b/README
@@ -89,9 +89,15 @@ get regarding a particular problem the sooner it'll be fixed -- usually.
 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, an explanation for why the patch is
+to the most recent test release (or, better, relative to the latest
+sources in the CVS repository), an explanation for why the patch is
 necessary or useful, and if at all possible, enough information to
-reproduce whatever problem prompted it.
+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
+
 
 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