summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2002-09-02 07:53:13 +0000
committerJim Meyering <jim@meyering.net>2002-09-02 07:53:13 +0000
commit585d13437cd4e90f17d570b5a1f3ef656091d619 (patch)
tree602d328c1edc143168dcb871a913b26035bb5ec3
parent496f29fa8ce6ddd5e71ba816282e0522c674ea7d (diff)
downloadcoreutils-585d13437cd4e90f17d570b5a1f3ef656091d619.tar.xz
A good problem report/patch includes diffs against
the most recent test release.
-rw-r--r--README15
1 files changed, 8 insertions, 7 deletions
diff --git a/README b/README
index 5546d5d74..f522dda2d 100644
--- a/README
+++ b/README
@@ -57,13 +57,14 @@ There are pretty many tests, but nowhere near as many as we need.
Additions and corrections are very welcome.
If you see a problem that you've already reported, feel free to re-report
-it -- it won't bother me to get a reminder. Besides, the more messages
-I 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,
-an explanation for why the patch is necessary or useful, and if at all
-possible, enough information to reproduce whatever problem prompted it.
+it -- it won't bother me to get a reminder. Besides, the more messages I
+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
+necessary or useful, and if at all possible, enough information to
+reproduce whatever problem prompted it.
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