diff options
| author | Jim Meyering <jim@meyering.net> | 2003-06-16 07:53:18 +0000 |
|---|---|---|
| committer | Jim Meyering <jim@meyering.net> | 2003-06-16 07:53:18 +0000 |
| commit | d2bebfab0e57faeb071b181e326bfc01e8171f67 (patch) | |
| tree | 51b52b7fa5414152f0ca5cd3dd8531a58f349cd8 | |
| parent | 40959940d9033f863fb9efebf02546a116990d55 (diff) | |
| download | coreutils-d2bebfab0e57faeb071b181e326bfc01e8171f67.tar.xz | |
Mention the CVS repository.
Encourage addition of test cases.
| -rw-r--r-- | README | 10 |
1 files changed, 8 insertions, 2 deletions
@@ -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 |