gnustandards ChangeLog maintain.texi

[Karl Berry]

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       11/12/03 01:06:26

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        (Standard Mailing Lists): recommend describing mailing lists in README 
and/or AUTHORS

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.144&r2=1.145
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.208&r2=1.209

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.144
retrieving revision 1.145
diff -u -b -r1.144 -r1.145
--- ChangeLog   12 Oct 2011 23:20:22 -0000      1.144
+++ ChangeLog   3 Dec 2011 01:06:25 -0000       1.145
@@ -1,3 +1,8 @@
+2011-12-02  Karl Berry  <address@hidden>
+
+       * maintain.texi (Standard Mailing Lists): recommending describing
+       mailing lists in README and/or AUTHORS.
+
 2011-10-12  Karl Berry  <address@hidden>
 
        * maintain.texi (Copyright Papers): new option for US contributors

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.208
retrieving revision 1.209
diff -u -b -r1.208 -r1.209
--- maintain.texi       12 Oct 2011 23:20:22 -0000      1.208
+++ maintain.texi       3 Dec 2011 01:06:26 -0000       1.209
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate October 12, 2011
address@hidden lastupdate December 2, 2011
 @c %**end of header
 
 @dircategory GNU organization
@@ -526,6 +526,11 @@
 automatically, if you are careful about the formatting of the change
 log entries.
 
+It is ok to include other email addresses, names, and program
+information in @file{AUTHORS}, such as bug-reporting information.
address@hidden Mailing Lists}.
+
+
 @node Copying from Other Packages
 @section Copying from Other Packages
 
@@ -1059,9 +1064,7 @@
 advertised bug-reporting email address should always be
 @address@hidden@@gnu.org}, to help show users that the program
 is a GNU package, but it is ok to set up that list to forward to another
-site if you prefer.  The package distribution should state the
-name of the bug-reporting list in a prominent place, and ask users to
-help us by reporting bugs there.
+site if you prefer.
 
 @cindex @email{bug-gnu-utils@@gnu.org}
 We also have a catch-all list, @email{bug-gnu-utils@@gnu.org}, which is
@@ -1084,6 +1087,14 @@
 @address@hidden for announcements (@pxref{Announcements}).
 Any other mailing lists you find useful can also be created.
 
+The package distribution should state the name of all the package's
+mailing lists in a prominent place, and ask users to help us by
+reporting bugs appropriately.  The top-level @file{README} file and/or
address@hidden file are good places.  Mailing list information should
+also be included in the manual and the package web pages (@pxref{Web
+Pages}).
+
+
 
 @node Creating Mailing Lists
 @section Creating Mailing Lists