Refer new feature discussion to bug-coreutils@gnu.org, rather than

bug-gnu-utils, now that the former is better known.

diff --git a/README b/README
index 3cf0bfdbc1ab2ebfa5457bd56a64e2f9d1746705..97f8cc17e4a64e078a758dd25fa76337c7b1e5c6 100644 (file)
--- a/README
+++ b/README
@@ -68,9 +68,9 @@ 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
-bug-gnu-utils@gnu.org (aka the gnu.utils.bug news group) including as
-much description and justification as you can.  Based on the feedback
-that generates, you may be able to convince us that it's worth adding.
+bug-coreutils@gnu.org including as much description and justification
+as you can.  Based on the feedback that generates, you may be able to
+convince us that it's worth adding.
 
 
 WARNING:  If you modify files like configure.in, m4/*.m4, aclocal.m4,