summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2010-04-27 07:17:44 -0700
committerKarl Berry <karl@freefriends.org>2010-04-27 07:17:44 -0700
commitf1a5e51859e28d9ff71107007d32b7c6aaa1fa02 (patch)
tree4f9e7d7825a6e1a3567a111661b06ba0dfc5eacb
parente98ea566d814c4e7df9f8988a01e4f970a427745 (diff)
downloadgnulib-f1a5e51859e28d9ff71107007d32b7c6aaa1fa02.tar.gz
autoupdate
-rwxr-xr-xbuild-aux/gnupload8
-rw-r--r--doc/maintain.texi64
2 files changed, 41 insertions, 31 deletions
diff --git a/build-aux/gnupload b/build-aux/gnupload
index d445075382..08cb842117 100755
--- a/build-aux/gnupload
+++ b/build-aux/gnupload
@@ -1,7 +1,7 @@
#!/bin/sh
# Sign files and upload them.
-scriptversion=2010-02-08.07; # UTC
+scriptversion=2010-04-25.17; # UTC
# Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software
# Foundation, Inc.
@@ -185,7 +185,7 @@ done
dprint()
{
- echo "Running $*..."
+ echo "Running $* ..."
}
if $dry_run; then
@@ -249,7 +249,7 @@ echo
if test $# -ne 0; then
for file
do
- echo "Signing $file..."
+ echo "Signing $file ..."
rm -f $file.sig
echo "$passphrase" | $dbg $GPG --passphrase-fd 0 -ba -o $file.sig $file
done
@@ -388,7 +388,7 @@ for dest in $to
do
for file
do
- echo "Uploading $file to $dest..."
+ echo "Uploading $file to $dest ..."
stmt=
files="$file $file.sig"
destdir=`echo $dest | sed 's/[^:]*://'`
diff --git a/doc/maintain.texi b/doc/maintain.texi
index 233c9f76e5..e736fb4123 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 April 14, 2010
+@set lastupdate April 25, 2010
@c %**end of header
@dircategory GNU organization
@@ -57,6 +57,7 @@ Texts. A copy of the license is included in the section entitled
@menu
* Preface::
* Getting Help::
+* Getting a GNU Account::
* Stepping Down::
* Recruiting Developers::
* Legal Matters::
@@ -76,17 +77,6 @@ Texts. A copy of the license is included in the section entitled
@end menu
-@macro gdgnuorgtext
-The directory @file{/gd/gnuorg} mentioned throughout this document is
-available on the general GNU server, currently
-@code{fencepost.gnu.org}. If you are the maintainer of a GNU package,
-you should have an account there. If you don't have one already,
-@url{http://www.gnu.org/software/README.accounts.html}. You can also
-ask for accounts for people who significantly help you in working on
-the package.
-@end macro
-
-
@node Preface
@chapter About This Document
@@ -119,14 +109,6 @@ instance via the web interface at
@url{http://lists.gnu.org/mailman/listinfo/gnustandards-commit}.
Archives are also available there.
-@gdgnuorgtext
-
-If you find that any GNU computer systems (@code{fencepost.gnu.org},
-@code{ftp.gnu.org}, @code{www.gnu.org}, @code{savannah.gnu.org},
-@dots{}) seem to be down, you can check the current status at
-@url{http://identi.ca/group/fsfstatus}. Most likely the problem, if
-it is at the FSF end, is already being worked on.
-
@cindex Piercy, Marge
This document uses the gender-neutral third-person pronouns ``person'',
``per'', ``pers'' and ``perself'' which were promoted, and perhaps
@@ -151,17 +133,45 @@ list of a few experienced GNU contributors who have offered to answer
questions for new maintainers.
@cindex advisory committee
-Finally, the GNU Advisory Committee helps to coordinate activities in
-the GNU project on behalf of RMS. If you have any organizational
-questions or concerns you can contact the committee members directly
-at @email{gnu-advisory@@gnu.org}. The committee holds a regular
-monthly meeting to discuss any issues that have been raised. The
-minutes of the meeting are sent to the @email{gnu-prog} list, and can
-also be found, along with additional information, in
+The GNU Advisory Committee helps to coordinate activities in the GNU
+project on behalf of RMS. If you have any organizational questions or
+concerns you can contact the committee at
+@email{gnu-advisory@@gnu.org}. The committee holds a regular monthly
+meeting to discuss any issues that have been raised. The minutes of
+the meeting are sent to the @code{gnu-prog} list, and can also be
+found, along with additional information, in
@file{/gd/gnuorg/advisory}.
+@node Getting a GNU Account
+@chapter Getting a GNU Account
+@cindex shell account, on fencepost
+@cindex @code{fencepost.gnu.org} GNU machine
+
+@c We want to repeat this text later, so define a macro.
+@macro gdgnuorgtext
+The directory @file{/gd/gnuorg} mentioned throughout this document is
+available on the general GNU server, currently
+@code{fencepost.gnu.org}. If you are the maintainer of a GNU package,
+you should have an account there. If you don't have one already,
+@url{http://www.gnu.org/software/README.accounts.html}. You can also
+ask for accounts for people who significantly help you in working on
+the package.
+@end macro
+
+@gdgnuorgtext
+
+@cindex down, when GNU machines are
+@cindex outage, of GNU machines
+@cindex @url{identi.ca/group/fsfstatus}
+If you find that any GNU computer systems (@code{fencepost.gnu.org},
+@code{ftp.gnu.org}, @code{www.gnu.org}, @code{savannah.gnu.org},
+@dots{}) seem to be down, you can check the current status at
+@url{http://identi.ca/group/fsfstatus}. Most likely the problem, if
+it can be alleviated at the FSF end, is already being worked on.
+
+
@node Stepping Down
@chapter Stepping Down
@cindex stepping down as maintainer