# HG changeset patch # User Karl Berry # Date 1291994446 28800 # Node ID 5f7a4e03ec7a215b14338959d5eb81ec59c94c2a # Parent 5667703dedaa0e41e8fe747447ea3676a883b099 autoupdate diff --git a/build-aux/gendocs.sh b/build-aux/gendocs.sh old mode 100755 new mode 100644 --- a/build-aux/gendocs.sh +++ b/build-aux/gendocs.sh @@ -2,9 +2,10 @@ # gendocs.sh -- generate a GNU manual in many formats. This script is # mentioned in maintain.texi. See the help message below for usage details. -scriptversion=2010-11-27.07 +scriptversion=2010-11-29.11 -# Copyright 2003-2010 Free Software Foundation, Inc. +# Copyright 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software +# Foundation, Inc. # # This program is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff --git a/doc/maintain.texi b/doc/maintain.texi --- 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 November 22, 2010 +@set lastupdate December 9, 2010 @c %**end of header @dircategory GNU organization @@ -1099,10 +1099,10 @@ @cindex version control It is very important to keep backup files of all source files of GNU. -You can do this using a source control system (such as RCS, CVS, Git, -@dots{}) if you like. The easiest way to use RCS or CVS is via the -Version Control library in Emacs (@pxref{VC Concepts,, Concepts of -Version Control, emacs, The GNU Emacs Manual}). +You can do this using a source control system (such as Bazaar, RCS, +CVS, Git, Subversion, @dots{}) if you like. The easiest way to use +RCS or CVS is via the Version Control library in Emacs (@pxref{VC +Concepts,, Concepts of Version Control, emacs, The GNU Emacs Manual}). The history of previous revisions and log entries is very important for future maintainers of the package, so even if you do not make it @@ -1113,15 +1113,14 @@ @cindex @code{savannah-hackers@@gnu.org} The GNU Project provides a server that GNU software packages can use for source control and other package needs: @code{savannah.gnu.org}. -You don't have to use this repository, but if you plan to allow public -read-only access to your development sources, it is convenient for -people to be able to find various GNU packages in a central place. -Savannah is managed by @email{savannah-hackers@@gnu.org}. +Savannah is managed by @email{savannah-hackers@@gnu.org}. For more +details on using and contributing to Savannah, see +@url{http://savannah.gnu.org/maintenance}. -All GNU maintainers are strongly encouraged to take advantage of -Savannah, as sharing such a central point can serve to foster a sense -of community among GNU developers and help in keeping up with project -management. +It's not a requirement, but all GNU maintainers are strongly +encouraged to take advantage of Savannah, as sharing such a central +point can serve to foster a sense of community among GNU developers +and help in keeping up with project management. @cindex @code{savannah-announce@@gnu.org} mailing list If you do use Savannah, please subscribe to the