From 7b9bf8a375833f5b00a9a491cbfe256d37263d1a Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Tue, 16 Aug 2011 06:35:34 -0700 Subject: [PATCH] autoupdate --- build-aux/config.sub | 8 +++++++- build-aux/texinfo.tex | 11 ++++++++--- doc/maintain.texi | 31 ++++++++++++++++--------------- 3 files changed, 31 insertions(+), 19 deletions(-) diff --git a/build-aux/config.sub b/build-aux/config.sub index f9fcdc879..63142cbf6 100755 --- a/build-aux/config.sub +++ b/build-aux/config.sub @@ -4,7 +4,7 @@ # 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, # 2011 Free Software Foundation, Inc. -timestamp='2011-06-03' +timestamp='2011-08-15' # This file is (in principle) common to ALL GNU software. # The presence of a machine in this file suggests that SOME GNU software @@ -246,6 +246,7 @@ case $basic_machine in # Recognize the basic CPU types without company name. # Some are omitted here because they have special meanings below. 1750a | 580 \ + | 32e[bl] | 64e[bl] \ | a29k \ | alpha | alphaev[4-8] | alphaev56 | alphaev6[78] | alphapca5[67] \ | alpha64 | alpha64ev[4-8] | alpha64ev56 | alpha64ev6[78] | alpha64pca5[67] \ @@ -351,6 +352,7 @@ case $basic_machine in ;; # Recognize the basic CPU types with company name. 580-* \ + | 32e[bl]-* | 64e[bl]-* \ | a29k-* \ | alpha-* | alphaev[4-8]-* | alphaev56-* | alphaev6[78]-* \ | alpha64-* | alpha64ev[4-8]-* | alpha64ev56-* | alpha64ev6[78]-* \ @@ -813,6 +815,10 @@ case $basic_machine in basic_machine=i370-ibm os=-mvs ;; + nacl) + basic_machine=32el-unknown + os=-nacl + ;; ncr3000) basic_machine=i486-ncr os=-sysv4 diff --git a/build-aux/texinfo.tex b/build-aux/texinfo.tex index fd22fd685..a7f94f96d 100644 --- a/build-aux/texinfo.tex +++ b/build-aux/texinfo.tex @@ -3,7 +3,7 @@ % Load plain if necessary, i.e., if running under initex. \expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi % -\def\texinfoversion{2011-05-23.16} +\def\texinfoversion{2011-08-14.17} % % Copyright 1985, 1986, 1988, 1990, 1991, 1992, 1993, 1994, 1995, % 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, @@ -5855,7 +5855,6 @@ end % This is purely so the last item on the list is a known \penalty > % 10000. This is so \startdefun can avoid allowing breakpoints after % section headings. Otherwise, it would insert a valid breakpoint between: - % % @section sec-whatever % @deffn def-whatever \penalty 10001 @@ -6273,6 +6272,12 @@ end \normbskip=\baselineskip \normpskip=\parskip \normlskip=\lineskip % Flag to tell @lisp, etc., not to narrow margin. \let\nonarrowing = t% + % + % If this cartouche directly follows a sectioning command, we need the + % \parskip glue (backspaced over by default) or the cartouche can + % collide with the section heading. + \ifnum\lastpenalty>10000 \vskip\parskip \fi + % \vbox\bgroup \baselineskip=0pt\parskip=0pt\lineskip=0pt \carttop @@ -6286,7 +6291,7 @@ end \lineskip=\normlskip \parskip=\normpskip \vskip -\parskip - \comment % For explanation, see the end of \def\group. + \comment % For explanation, see the end of def\group. } \def\Ecartouche{% \ifhmode\par\fi diff --git a/doc/maintain.texi b/doc/maintain.texi index 06ed3f430..241663e3d 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 June 30, 2011 +@set lastupdate August 14, 2011 @c %**end of header @dircategory GNU organization @@ -93,8 +93,8 @@ In addition to this document, please read and follow the GNU Coding Standards (@pxref{Top, , Contents, standards, GNU Coding Standards}). @cindex @code{bug-standards@@gnu.org} email address -@cindex Savannah repository for gnustandards -@cindex gnustandards project repository +@cindex Savannah repository for @code{gnustandards} +@cindex @code{gnustandards} project repository Please send corrections or suggestions for this document to @email{bug-standards@@gnu.org}. If you make a suggestion, please include suggested new wording if you can. We prefer a context diff to @@ -200,12 +200,11 @@ If you have an idea for who should take over, please tell maintainer needs the GNU Project's confirmation, but your judgment that a person is capable of doing the job will carry a lot of weight. -As your final act as maintainer, it would be helpful to set up the -package under @code{savannah.gnu.org} if it is not there already -(@pxref{Old Versions}). This will make it much easier for the new -maintainer to pick up where you left off and will ensure that the -source tree is not misplaced if it takes us a while to find a new -maintainer. +As your final act as maintainer, it would be helpful to set up or +update the package under @code{savannah.gnu.org} (@pxref{Old +Versions}). This will make it much easier for the new maintainer to +pick up where you left off and will ensure that the source tree is not +misplaced if it takes us a while to find a new maintainer. @node Recruiting Developers @@ -1170,8 +1169,8 @@ useful for your package. 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 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 +CVS, Git, Subversion, @dots{}) if you like. An easy way to use +many such systems is via the Version Control library in Emacs (@pxref{Introduction to VC,, Introduction to Version Control, emacs, The GNU Emacs Manual}). @@ -1182,16 +1181,18 @@ change log that you would not want to hand over to another maintainer some day. @cindex @code{savannah-hackers@@gnu.org} -The GNU Project provides a server that GNU software packages can use +The GNU Project provides a server that GNU packages can use for source control and other package needs: @code{savannah.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}. -It's not a requirement, but all GNU maintainers are strongly +It's not an absolute 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. +point can serve to foster a sense of community among GNU developers as +well as help in keeping up with project management. Please don't mark +Savannah projects for GNU packages as private; that defeats a large +part of the purpose of using Savannah in the first place. @cindex @code{savannah-announce@@gnu.org} mailing list If you do use Savannah, please subscribe to the -- 2.11.0