From 46519aac67ad6faa169504659be386c167de46c3 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Sat, 10 Dec 2011 08:23:45 -0800 Subject: [PATCH] autoupdate (cherry picked from commit 84461035138fcfc32178d1be6c1a9d0a9b21854e) --- build-aux/depcomp | 4 ++-- doc/maintain.texi | 19 +++++++++++++++---- doc/standards.texi | 19 +++++++++++-------- 3 files changed, 28 insertions(+), 14 deletions(-) diff --git a/build-aux/depcomp b/build-aux/depcomp index 9825d56d7..bd0ac0895 100755 --- a/build-aux/depcomp +++ b/build-aux/depcomp @@ -1,7 +1,7 @@ #! /bin/sh # depcomp - compile a program generating dependencies as side-effects -scriptversion=2011-04-16.09; # UTC +scriptversion=2011-12-04.11; # UTC # Copyright (C) 1999, 2000, 2003, 2004, 2005, 2006, 2007, 2009, 2010, # 2011 Free Software Foundation, Inc. @@ -44,7 +44,7 @@ Environment variables: object Object file output by `PROGRAMS ARGS'. DEPDIR directory where to store dependencies. depfile Dependency file to output. - tmpdepfile Temporary file to use when outputing dependencies. + tmpdepfile Temporary file to use when outputting dependencies. libtool Whether libtool is used (yes/no). Report bugs to . diff --git a/doc/maintain.texi b/doc/maintain.texi index cedbeb79d..40e37ba30 100644 --- a/doc/maintain.texi +++ b/doc/maintain.texi @@ -5,7 +5,7 @@ @c For double-sided printing, uncomment: @c @setchapternewpage odd @c This date is automagically updated when you save this file: -@set lastupdate October 12, 2011 +@set lastupdate December 2, 2011 @c %**end of header @dircategory GNU organization @@ -526,6 +526,11 @@ trivial to matter for copyright purposes. Later on you can update the 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. +@xref{Standard Mailing Lists}. + + @node Copying from Other Packages @section Copying from Other Packages @@ -1059,9 +1064,7 @@ programs have their own special lists for sending bug reports. The advertised bug-reporting email address should always be @samp{bug-@var{package}@@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 @@ If you wish, you can also have a mailing list @samp{info-@var{package}} 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 +@file{AUTHORS} 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 diff --git a/doc/standards.texi b/doc/standards.texi index 54336c6bc..b7ec606fa 100644 --- a/doc/standards.texi +++ b/doc/standards.texi @@ -3,7 +3,7 @@ @setfilename standards.info @settitle GNU Coding Standards @c This date is automagically updated when you save this file: -@set lastupdate September 25, 2011 +@set lastupdate December 4, 2011 @c %**end of header @dircategory GNU organization @@ -614,8 +614,8 @@ The only sensible exceptions would be utilities specifically intended for interface to certain types of terminals or printers that can't handle those characters. Whenever possible, try to make programs work properly with -sequences of bytes that represent multibyte characters, using encodings -such as UTF-8 and others. +sequences of bytes that represent multibyte characters; +UTF-8 is the most important. @cindex error messages Check every system call for an error return, unless you know you wish @@ -769,7 +769,9 @@ Line numbers should start from 1 at the beginning of the file, and column numbers should start from 1 at the beginning of the line. (Both of these conventions are chosen for compatibility.) Calculate column numbers assuming that space and all ASCII printing characters have -equal width, and assuming tab stops every 8 columns. +equal width, and assuming tab stops every 8 columns. For non-ASCII +characters, Unicode character widths should be used when in a UTF-8 +locale; GNU libc and GNU gnulib provide suitable @code{wcwidth} functions. The error message can also give both the starting and ending positions of the erroneous text. There are several formats so that you can @@ -3170,11 +3172,12 @@ contexts, unless there is good reason to do something else because of the application domain. For example, if source code deals with the French Revolutionary calendar, it is OK if its literal strings contain accented characters in month names like ``Flor@'eal''. Also, it is OK -to use non-ASCII characters to represent proper names of contributors in -change logs (@pxref{Change Logs}). +(but not required) to use non-ASCII characters to represent proper +names of contributors in change logs (@pxref{Change Logs}). If you need to use non-ASCII characters, you should normally stick with -one encoding, as one cannot in general mix encodings reliably. +one encoding, certainly within a single file. UTF-8 is likely to be +the best choice. @node Quote Characters @@ -4163,7 +4166,7 @@ things in the GNU system even if they are free---they are outside the scope of what a software distribution needs to include. Referring to a web site that describes or recommends a non-free -program is promoting that program, so please do not make links (or +program is promoting that program, so please do not make links to (or mention by name) web sites that contain such material. This policy is relevant particularly for the web pages for a GNU package. -- 2.11.0