[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/prep/maintain index.html maintain.dvi.gz ma...
|
From: |
Mike Gerwitz |
|
Subject: |
www/prep/maintain index.html maintain.dvi.gz ma... |
|
Date: |
Wed, 21 Nov 2018 21:47:55 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: Mike Gerwitz <mikegerwitz> 18/11/21 21:47:53
Modified files:
prep/maintain : index.html maintain.dvi.gz maintain.html
maintain.html.gz maintain.html_node.tar.gz
maintain.info.tar.gz maintain.pdf
maintain.texi.tar.gz maintain.txt
maintain.txt.gz
prep/maintain/html_node: Announcements.html
Automated-FTP-Uploads.html
Automated-Upload-Procedure.html
Automated-Upload-Registration.html
Binary-Distribution.html
CVS-Keywords-in-Web-Pages.html
Canonical-License-Sources.html
Clean-Ups.html
Copying-from-Other-Packages.html
Copyright-Notices.html
Copyright-Papers.html
Creating-Mailing-Lists.html
Crediting-Authors.html
Distribution-Patches.html
Distribution-on-ftp_002egnu_002eorg.html
Distribution-tar-Files.html
Distributions.html Donations.html
Ethical-and-Philosophical-Consideration.html
External-Libraries.html
FSF_002dCopyrighted-Package.html
FTP-Upload-Directive-File-_002d-v1_002e0.html
FTP-Upload-Directive-File-_002d-v1_002e1.html
FTP-Upload-Directive-File.html
FTP-Upload-Directory-Trees.html
FTP-Upload-File-Replacement.html
FTP-Upload-Release-File-Triplet.html
FTP-Upload-Standalone-Directives.html
Free-Software-Directory.html
Free-Software-and-Open-Source.html
Freedom-for-Web-Pages.html
GNU-Accounts-and-Resources.html
GNU-Free-Documentation-License.html
GNU-and-Linux.html Getting-Help.html
Hosting-for-Web-Pages.html Hosting.html
Humor.html Index.html
Interviews-and-Speeches.html
Invoking-gendocs_002esh.html
Legal-Matters.html
Legally-Significant.html
License-Notices-for-Code.html
License-Notices-for-Documentation.html
License-Notices-for-Other-Files.html
License-Notices.html
Licensing-of-GNU-Packages.html
Mail.html Manuals-on-Web-Pages.html
Non_002dFSF_002dCopyrighted-Package.html
Old-Versions.html Other-Politics.html
Platforms.html Preface.html
Recording-Contributors.html
Recruiting-Developers.html
Replying-to-Mail.html
Standard-Mailing-Lists.html
Stepping-Down.html Terminology.html
Test-Releases.html
Using-the-Proofreaders-List.html
Web-Pages.html index.html
Log message:
prep/maintain: UTF-8 encoding
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/index.html?cvsroot=www&r1=1.116&r2=1.117
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.dvi.gz?cvsroot=www&rev=1.109
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.html?cvsroot=www&r1=1.111&r2=1.112
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.html.gz?cvsroot=www&rev=1.110
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.html_node.tar.gz?cvsroot=www&rev=1.110
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.info.tar.gz?cvsroot=www&rev=1.109
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.pdf?cvsroot=www&rev=1.110
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.texi.tar.gz?cvsroot=www&rev=1.109
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.txt?cvsroot=www&r1=1.111&r2=1.112
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.txt.gz?cvsroot=www&rev=1.109
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Announcements.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Automated-FTP-Uploads.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Automated-Upload-Procedure.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Automated-Upload-Registration.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Binary-Distribution.html?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/CVS-Keywords-in-Web-Pages.html?cvsroot=www&r1=1.104&r2=1.105
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Canonical-License-Sources.html?cvsroot=www&r1=1.89&r2=1.90
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Clean-Ups.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Copying-from-Other-Packages.html?cvsroot=www&r1=1.93&r2=1.94
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Copyright-Notices.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Copyright-Papers.html?cvsroot=www&r1=1.107&r2=1.108
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Creating-Mailing-Lists.html?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Crediting-Authors.html?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Distribution-Patches.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Distribution-on-ftp_002egnu_002eorg.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Distribution-tar-Files.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Distributions.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Donations.html?cvsroot=www&r1=1.48&r2=1.49
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Ethical-and-Philosophical-Consideration.html?cvsroot=www&r1=1.106&r2=1.107
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/External-Libraries.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FSF_002dCopyrighted-Package.html?cvsroot=www&r1=1.31&r2=1.32
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html?cvsroot=www&r1=1.95&r2=1.96
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html?cvsroot=www&r1=1.95&r2=1.96
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Directive-File.html?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Directory-Trees.html?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-File-Replacement.html?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Release-File-Triplet.html?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Standalone-Directives.html?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Free-Software-Directory.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Free-Software-and-Open-Source.html?cvsroot=www&r1=1.107&r2=1.108
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Freedom-for-Web-Pages.html?cvsroot=www&r1=1.64&r2=1.65
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/GNU-Accounts-and-Resources.html?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/GNU-Free-Documentation-License.html?cvsroot=www&r1=1.82&r2=1.83
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/GNU-and-Linux.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Getting-Help.html?cvsroot=www&r1=1.59&r2=1.60
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Hosting-for-Web-Pages.html?cvsroot=www&r1=1.64&r2=1.65
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Hosting.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Humor.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Index.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Interviews-and-Speeches.html?cvsroot=www&r1=1.30&r2=1.31
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Invoking-gendocs_002esh.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Legal-Matters.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Legally-Significant.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/License-Notices-for-Code.html?cvsroot=www&r1=1.89&r2=1.90
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/License-Notices-for-Documentation.html?cvsroot=www&r1=1.89&r2=1.90
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/License-Notices-for-Other-Files.html?cvsroot=www&r1=1.89&r2=1.90
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/License-Notices.html?cvsroot=www&r1=1.107&r2=1.108
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Licensing-of-GNU-Packages.html?cvsroot=www&r1=1.45&r2=1.46
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Mail.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Manuals-on-Web-Pages.html?cvsroot=www&r1=1.64&r2=1.65
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Non_002dFSF_002dCopyrighted-Package.html?cvsroot=www&r1=1.31&r2=1.32
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Old-Versions.html?cvsroot=www&r1=1.107&r2=1.108
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Other-Politics.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Platforms.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Preface.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Recording-Contributors.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Recruiting-Developers.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Replying-to-Mail.html?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Standard-Mailing-Lists.html?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Stepping-Down.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Terminology.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Test-Releases.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Using-the-Proofreaders-List.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/Web-Pages.html?cvsroot=www&r1=1.105&r2=1.106
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/index.html?cvsroot=www&r1=1.105&r2=1.106
Patches:
Index: index.html
===================================================================
RCS file: /web/www/www/prep/maintain/index.html,v
retrieving revision 1.116
retrieving revision 1.117
diff -u -b -r1.116 -r1.117
--- index.html 14 Nov 2018 02:29:47 -0000 1.116
+++ index.html 22 Nov 2018 02:47:48 -0000 1.117
@@ -5,7 +5,7 @@
<h2>Information for maintainers of GNU software</h2>
<address>Free Software Foundation</address>
-<address>last updated November 13, 2018</address>
+<address>last updated November 21, 2018</address>
<p>This manual (maintain) is available in the following formats:</p>
@@ -23,13 +23,13 @@
<li><a href="maintain.info.tar.gz">Info document
(48K bytes gzipped tar file)</a>.</li>
<li><a href="maintain.txt">ASCII text
- (144K bytes)</a>.</li>
+ (148K bytes)</a>.</li>
<li><a href="maintain.txt.gz">ASCII text compressed
(48K bytes gzipped)</a>.</li>
<li><a href="maintain.dvi.gz">TeX dvi file
(84K bytes gzipped)</a>.</li>
<li><a href="maintain.pdf">PDF file
- (444K bytes)</a>.</li>
+ (448K bytes)</a>.</li>
<li><a href="maintain.texi.tar.gz">Texinfo source
(108K bytes gzipped tar file).</a></li>
</ul>
Index: maintain.dvi.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.dvi.gz,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -b -r1.108 -r1.109
Binary files /var/tmp/cvsglnMQT and /var/tmp/cvsRFAjUn differ
Index: maintain.html
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.html,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -b -r1.111 -r1.112
--- maintain.html 14 Nov 2018 02:29:47 -0000 1.111
+++ maintain.html 22 Nov 2018 02:47:50 -0000 1.112
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
@@ -168,7 +168,7 @@
<a name="Version"></a>
<h1 class="top">Version</h1>
-<p>Information for maintainers of GNU software, last updated October 24, 2018.
+<p>Information for maintainers of GNU software, last updated November 21, 2018.
</p>
<p>Copyright © 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
@@ -284,7 +284,7 @@
work, and to enable per to feel person has done the right thing.”
</p>
<p>This release of the GNU Maintainer Information was last updated
-October 24, 2018.
+November 21, 2018.
</p>
<hr>
@@ -2944,9 +2944,9 @@
humorous, so we do not defend every joke obtusely to the bitter end.
But <em>the fact that it is a joke</em> is not a valid objection.
</p>
-<p>There are people who frown on anything that is slightly risqué or
+<p>There are people who frown on anything that is slightly risqué or
controversial, including jokes. It would be a terrible shame for that
-attitude to prevail, so our policy is that the occasional risqué joke
+attitude to prevail, so our policy is that the occasional risqué joke
is ok. GNU is a 21st century project, not a 19th.
</p>
<hr>
Index: maintain.html.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.html.gz,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -b -r1.109 -r1.110
Binary files /var/tmp/cvsgHONxY and /var/tmp/cvsRMbRNs differ
Index: maintain.html_node.tar.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.html_node.tar.gz,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -b -r1.109 -r1.110
Binary files /var/tmp/cvs1CcRQX and /var/tmp/cvsnBbpcs differ
Index: maintain.info.tar.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.info.tar.gz,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -b -r1.108 -r1.109
Binary files /var/tmp/cvsuBxEE0 and /var/tmp/cvsBxqC5u differ
Index: maintain.pdf
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.pdf,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -b -r1.109 -r1.110
Binary files /var/tmp/cvsjlUoj2 and /var/tmp/cvsUxO9Qw differ
Index: maintain.texi.tar.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.texi.tar.gz,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -b -r1.108 -r1.109
Binary files /var/tmp/cvsMzdgb5 and /var/tmp/cvsJJ98Oz differ
Index: maintain.txt
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.txt,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -b -r1.111 -r1.112
--- maintain.txt 14 Nov 2018 02:29:48 -0000 1.111
+++ maintain.txt 22 Nov 2018 02:47:51 -0000 1.112
@@ -31,7 +31,7 @@
11.1 Distribution tar Files
11.2 Distribution Patches
11.3 Binary Distribution for Nonfree Platforms
- 11.4 Distribution on 'ftp.gnu.org'
+ 11.4 Distribution on âftp.gnu.orgâ
11.5 Test Releases
11.6 Automated FTP Uploads
11.6.1 Automated Upload Registration
@@ -48,7 +48,7 @@
12.1 Hosting for Web Pages
12.2 Freedom for Web Pages
12.3 Manuals on Web Pages
- 12.3.1 Invoking 'gendocs.sh'
+ 12.3.1 Invoking âgendocs.shâ
12.4 CVS Keywords in Web Pages
13 Ethical and Philosophical Consideration
14 Humor and GNU
@@ -66,10 +66,10 @@
Version
*******
-Information for maintainers of GNU software, last updated October 24,
+Information for maintainers of GNU software, last updated November 21,
2018.
- Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
+ Copyright © 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012,
2013, 2014, 2015, 2016, 2017 Free Software Foundation, Inc.
@@ -77,8 +77,8 @@
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
-copy of the license is included in the section entitled "GNU Free
-Documentation License".
+copy of the license is included in the section entitled âGNU Free
+Documentation Licenseâ.
1 About This Document
*********************
@@ -93,53 +93,53 @@
In addition to this document, please read and follow the GNU Coding
Standards (*note Contents: (standards)Top.). You may also usefully
-check the "Tips for new GNU maintainers"
+check the âTips for new GNU maintainersâ
(<https://www.gnu.org/software/maintainer-tips>), a list of the most
important things you will need to do as a new maintainer.
Please send corrections or suggestions for this document to
<address@hidden>. If you make a suggestion, please include
suggested new wording if you can. We prefer a context diff to the
-Texinfo source, but if that's difficult for you, you can make a diff for
+Texinfo source, but if thatâs difficult for you, you can make a diff for
some other version of this document, or propose it in any way that makes
it clear. The source repository for this document can be found at
<https://savannah.gnu.org/projects/gnustandards>.
If you want to receive diffs for every change to these GNU documents,
-join the mailing list 'address@hidden', for instance via
+join the mailing list address@hidden, for instance via
the web interface at
<https://lists.gnu.org/mailman/listinfo/gnustandards-commit>. Archives
are also available there.
- This document uses the gender-neutral third-person pronouns "person",
-"per", "pers" and "perself" which were promoted, and perhaps invented,
-by Marge Piercy in 'Woman on the Edge of Time'. They are used just like
-"she", "her", "hers" and "herself", except that they apply equally to
-males and females. For example, "Person placed per new program under
+ This document uses the gender-neutral third-person pronouns âpersonâ,
+âperâ, âpersâ and âperselfâ which were promoted, and perhaps
invented,
+by Marge Piercy in âWoman on the Edge of Timeâ. They are used just like
+âsheâ, âherâ, âhersâ and âherselfâ, except that they apply
equally to
+males and females. For example, âPerson placed per new program under
the GNU GPL, to let the public benefit from per work, and to enable per
-to feel person has done the right thing."
+to feel person has done the right thing.â
This release of the GNU Maintainer Information was last updated
-October 24, 2018.
+November 21, 2018.
2 Getting Help
**************
If you have any general questions or encounter a situation where it
-isn't clear how to get something done or who to ask, you (as a GNU
+isnât clear how to get something done or who to ask, you (as a GNU
contributor) can always write to <address@hidden>, which is a list of a
few experienced GNU folks who have volunteered to answer questions. Any
-GNU-related question is fair game for the 'mentors' list.
+GNU-related question is fair game for the âmentorsâ list.
The GNU Advisory Committee helps to coordinate activities in the GNU
project on behalf of RMS (Richard Stallman, the Chief GNUisance). If
you have any organizational questions or concerns you can contact the
committee at <address@hidden>. See
<https://www.gnu.org/contact/gnu-advisory.html> for the current
-committee members. Additional information is in '/gd/gnuorg/advisory'.
+committee members. Additional information is in â/gd/gnuorg/advisoryâ.
- If you find that any GNU computer systems ('fencepost.gnu.org',
-'ftp.gnu.org', 'www.gnu.org', 'savannah.gnu.org', ...) seem to be down,
+ If you find that any GNU computer systems (âfencepost.gnu.orgâ,
+âftp.gnu.orgâ, âwww.gnu.orgâ, âsavannah.gnu.orgâ, â¦) seem to be
down,
you can check the current status at <https://quitter.im/fsfstatus>.
Most likely the problem, if it can be alleviated at the FSF end, is
already being worked on.
@@ -152,10 +152,10 @@
3 GNU Accounts and Resources
****************************
-The directory '/gd/gnuorg' mentioned throughout this document is
-available on the general GNU server, currently 'fencepost.gnu.org'. If
+The directory â/gd/gnuorgâ mentioned throughout this document is
+available on the general GNU server, currently â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, see
+there. If you donât have one already, see
<https://www.gnu.org/software/README.accounts.html>. You can also ask
for accounts for people who significantly help you in working on the
package. Such GNU login accounts include email (see
@@ -165,17 +165,17 @@
<https://www.gnu.org/software/devel.html>, as well as throughout this
document. In brief:
- * Login accounts (see above).
+ ⢠Login accounts (see above).
- * Version control (*note Old Versions::).
+ ⢠Version control (*note Old Versions::).
- * Mailing lists (*note Mail::).
+ ⢠Mailing lists (*note Mail::).
- * Web pages (*note Web Pages::).
+ ⢠Web pages (*note Web Pages::).
- * Mirrored release areas (*note Distributions::).
+ ⢠Mirrored release areas (*note Distributions::).
- * Pre-release portability testing, both automated (via Hydra) and on
+ ⢠Pre-release portability testing, both automated (via Hydra) and on
request (via volunteers).
4 Stepping Down
@@ -185,18 +185,18 @@
decades. But sometimes for various reasons maintainers decide to step
down.
- If you're the official maintainer of a GNU package and you decide to
+ If youâre the official maintainer of a GNU package and you decide to
step down, please inform the GNU Project (<address@hidden>). We
need to know that the package no longer has a maintainer, so we can look
for and appoint a new maintainer.
If you have an idea for who should take over, please tell
<address@hidden> your suggestion. The appointment of a new
-maintainer needs the GNU Project's confirmation, but your judgment that
+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 or
-update the package under 'savannah.gnu.org' (*note Old Versions::).
+update the package under âsavannah.gnu.orgâ (*note 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.
@@ -204,18 +204,18 @@
5 Recruiting Developers
***********************
-Unless your package is a fairly small, you probably won't do all the
+Unless your package is a fairly small, you probably wonât do all the
work on it yourself. Most maintainers recruit other developers to help.
Sometimes people will offer to help. Some of them will be capable,
-while others will not. It's up to you to determine who provides useful
+while others will not. Itâs up to you to determine who provides useful
help, and encourage those people to participate more.
Some of the people who offer to help will support the GNU Project,
while others may be interested for other reasons. Some will support the
goals of the Free Software Movement, but some may not. They are all
-welcome to help with the work--we don't ask people's views or
-motivations before they contribute to GNU packages.
+welcome to help with the workâwe donât ask peopleâs views or motivations
+before they contribute to GNU packages.
As a consequence, you cannot expect all contributors to support the
GNU Project, or to have a concern for its policies and standards. So
@@ -227,11 +227,11 @@
Sometimes a package has several co-maintainers who share the role of
maintainer. Unlike developers who help, co-maintainers have actually
been appointed jointly as the maintainers of the package, and they carry
-out the maintainer's functions together. If you would like to propose
+out the maintainerâs functions together. If you would like to propose
some of your developers as co-maintainers, please contact
<address@hidden>.
- We're happy to acknowledge all major contributors to GNU packages on
+ Weâre happy to acknowledge all major contributors to GNU packages on
the <https://www.gnu.org/people/people.html> web page. Please send an
entry for yourself to <address@hidden>, and feel free to suggest it
to other significant developers on your package.
@@ -261,36 +261,36 @@
_Before_ incorporating significant changes, make sure that the person
who wrote the changes has signed copyright papers and that the Free
Software Foundation has received and signed them. We may also need an
-employer's disclaimer from the person's employer, which confirms that
-the work was not part of the person's job and the employer makes no
-claim on it. However, a copy of the person's employment contract,
-showing that the employer can't claim any rights to this work, is often
+employerâs disclaimer from the personâs employer, which confirms that
+the work was not part of the personâs job and the employer makes no
+claim on it. However, a copy of the personâs employment contract,
+showing that the employer canât claim any rights to this work, is often
sufficient.
- If the employer does claim the work was part of the person's job, and
+ If the employer does claim the work was part of the personâs job, and
there is no clear basis to say that claim is invalid, then we have to
consider it valid. Then the person cannot assign copyright, but the
employer can. Many companies have done this. Please ask the
-appropriate managers to contact 'address@hidden'.
+appropriate managers to contact address@hidden
To check whether papers have been received, look in
-'/gd/gnuorg/copyright.list'. If you can't look there directly,
+â/gd/gnuorg/copyright.listâ. If you canât look there directly,
<address@hidden> can check for you. Our clerk can also check for
papers that are waiting to be entered and inform you when expected
papers arrive.
- The directory '/gd/gnuorg' mentioned throughout this document is
-available on the general GNU server, currently 'fencepost.gnu.org'. If
+ The directory â/gd/gnuorgâ mentioned throughout this document is
+available on the general GNU server, currently â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, see
+there. If you donât have one already, see
<https://www.gnu.org/software/README.accounts.html>. You can also ask
for accounts for people who significantly help you in working on the
package. Such GNU login accounts include email (see
<https://www.fsf.org/about/systems/sending-mail-via-fencepost>).
In order for the contributor to know person should sign papers, you
-need to ask per for the necessary papers. If you don't know per well,
-and you don't know that person is used to our ways of handling copyright
+need to ask per for the necessary papers. If you donât know per well,
+and you donât know that person is used to our ways of handling copyright
papers, then it might be a good idea to raise the subject with a message
like this:
@@ -303,40 +303,40 @@
change in the public domain, so that we can install it in PACKAGE?
If the contributor then wants more information, you can send per the
-file '/gd/gnuorg/conditions.text', which explains per options (assign
+file â/gd/gnuorg/conditions.textâ, which explains per options (assign
vs. disclaim) and their consequences.
Once the conversation is under way and the contributor is ready for
more details, you should send one of the templates that are found in the
-directory '/gd/gnuorg/Copyright/'; they are also available from the
-'doc/Copyright/' directory of the 'gnulib' project at
+directory â/gd/gnuorg/Copyright/â; they are also available from the
+âdoc/Copyright/â directory of the âgnulibâ project at
<https://savannah.gnu.org/projects/gnulib>. This section explains which
-templates you should use in which circumstances. *Please don't use any
-of the templates except for those listed here, and please don't change
+templates you should use in which circumstances. *Please donât use any
+of the templates except for those listed here, and please donât change
the wording.*
Once the conversation is under way, you can send the contributor the
precise wording and instructions by email. Before you do this, make
sure to get the current version of the template you will use! We change
-these templates occasionally--don't keep using an old version.
+these templates occasionallyâdonât keep using an old version.
For large changes, ask the contributor for an assignment. Send per a
-copy of the file 'request-assign.changes'. (Like all the 'request-'
-files, it is in '/gd/gnuorg/Copyright' and in 'gnulib'.)
+copy of the file ârequest-assign.changesâ. (Like all the ârequest-â
+files, it is in â/gd/gnuorg/Copyrightâ and in âgnulibâ.)
For medium to small changes, request a personal disclaimer by sending
-per the file 'request-disclaim.changes'.
+per the file ârequest-disclaim.changesâ.
If the contributor is likely to keep making changes, person might
want to sign an assignment for all per future changes to the program.
So it is useful to offer per that alternative. If person wants to do it
-that way, send per the 'request-assign.future'.
+that way, send per the ârequest-assign.futureâ.
- When you send a 'request-' file, you don't need to fill in anything
+ When you send a ârequest-â file, you donât need to fill in anything
before sending it. Just send the file verbatim to the contributor. The
file gives per instructions for how to ask the FSF to mail per the
-papers to sign. The 'request-' file also raises the issue of getting an
-employer's disclaimer from the contributor's employer.
+papers to sign. The ârequest-â file also raises the issue of getting an
+employerâs disclaimer from the contributorâs employer.
When the contributor emails the form to the FSF, the FSF sends per an
electronic (usually PDF) copy of the assignment. This, or whatever
@@ -358,30 +358,30 @@
For less common cases, we have template files you should send to the
contributor. Be sure to fill in the name of the person and the name of
-the program in these templates, where it says 'NAME OF PERSON' and 'NAME
-OF PROGRAM', before sending; otherwise person might sign without
+the program in these templates, where it says âNAME OF PERSONâ and âNAME
+OF PROGRAMâ, before sending; otherwise person might sign without
noticing them, and the papers would be useless. Note that in some
templates there is more than one place to put the name of the program or
the name of the person; be sure to change all of them. All the
-templates raise the issue of an employer's disclaimer as well.
+templates raise the issue of an employerâs disclaimer as well.
You do not need to ask for separate papers for a manual that is
distributed only in the software package it describes. But if we
sometimes distribute the manual separately (for instance, if we publish
it as a book), then we need separate legal papers for changes in the
-manual. For smaller changes, use 'disclaim.changes.manual'; for larger
-ones, use 'assign.changes.manual'. To cover both past and future
-changes to a manual, you can use 'assign.future.manual'. For a
-translation of a manual, use 'assign.translation.manual'.
+manual. For smaller changes, use âdisclaim.changes.manualâ; for larger
+ones, use âassign.changes.manualâ. To cover both past and future
+changes to a manual, you can use âassign.future.manualâ. For a
+translation of a manual, use âassign.translation.manualâ.
For translations of program strings (as used by GNU Gettext, for
example; *note (standards)Internationalization::), use
-'disclaim.translation'. If you make use of the Translation Project
+âdisclaim.translationâ. If you make use of the Translation Project
(<https://translationproject.org>) facilities, please check with the TP
coordinators that they have sent the contributor the papers; if they
-haven't, then you should send the papers. In any case, you should wait
+havenât, then you should send the papers. In any case, you should wait
for the confirmation from the FSF that the signed papers have been
-received and accepted before integrating the new contributor's material,
+received and accepted before integrating the new contributorâs material,
as usual.
If a contributor is reluctant to sign an assignment for a large
@@ -393,15 +393,15 @@
If you maintain a collection of programs, occasionally someone will
contribute an entire separate program or manual that should be added to
-the collection. Then you can use the files 'request-assign.program',
-'disclaim.program', 'assign.manual', and 'disclaim.manual'. We very
+the collection. Then you can use the files ârequest-assign.programâ,
+âdisclaim.programâ, âassign.manualâ, and âdisclaim.manualâ. We
very
much prefer an assignment for a new separate program or manual, unless
it is quite small, but a disclaimer is acceptable if the contributor
insists on handling the matter that way.
If a contributor wants the FSF to publish only a pseudonym, that is
ok. The contributor should say this, and state the desired pseudonym,
-when answering the 'request-' form. The actual legal papers will use
+when answering the ârequest-â form. The actual legal papers will use
the real name, but the FSF will publish only the pseudonym. When using
one of the other forms, fill in the real name but ask the contributor to
discuss the use of a pseudonym with <address@hidden> before sending back
@@ -413,7 +413,7 @@
If you are not sure what to do, then please ask <address@hidden> for
advice; if the contributor asks you questions about the meaning and
-consequences of the legal papers, and you don't know the answers, you
+consequences of the legal papers, and you donât know the answers, you
can forward them to <address@hidden> and we will answer.
*Please do not try changing the wording of a template yourself. If
@@ -445,7 +445,7 @@
The credit should clearly say they did not contribute significant code
or text.
- When people's contributions are not legally significant because they
+ When peopleâs contributions are not legally significant because they
did not write code, do this by stating clearly what their contribution
was. For instance, you could write this:
@@ -455,8 +455,8 @@
* Masatake Yamato <address@hidden> (1999)
*/
-'Ideas by:' makes it clear that Mlynarik and Yamato here contributed
-only ideas, not code. Without the 'Ideas by:' note, several years from
+âIdeas by:â makes it clear that Mlynarik and Yamato here contributed
+only ideas, not code. Without the âIdeas by:â note, several years from
now we would find it hard to be sure whether they had contributed code,
and we might have to track them down and ask them.
@@ -466,8 +466,8 @@
should get copyright papers for all per changes before you install the
new change.
- If that is not so, you can install the small patch. Write '(tiny
-change)' after the patch author's name, like this:
+ If that is not so, you can install the small patch. Write â(tiny
+change)â after the patch authorâs name, like this:
2002-11-04 Robert Fenk <address@hidden> (tiny change)
@@ -478,14 +478,14 @@
very important. These records should say which files or parts of files
were written by each person, and which files or parts of files were
revised by each person. This should include installation scripts as
-well as manuals and documentation files--everything.
+well as manuals and documentation filesâeverything.
- These records don't need to be as detailed as a change log. They
-don't need to distinguish work done at different times, only different
-people. They don't need describe changes in more detail than which
-files or parts of a file were changed. And they don't need to say
-anything about the function or purpose of a file or change--the Register
-of Copyrights doesn't care what the text does, just who wrote or
+ These records donât need to be as detailed as a change log. They
+donât need to distinguish work done at different times, only different
+people. They donât need describe changes in more detail than which
+files or parts of a file were changed. And they donât need to say
+anything about the function or purpose of a file or changeâthe Register
+of Copyrights doesnât care what the text does, just who wrote or
contributed to which parts.
The list should also mention if certain files distributed in the same
@@ -505,19 +505,19 @@
Note: GAS is distributed with the files obstack.c and obstack.h, but
they are considered a separate package, not part of GAS proper.
- Please keep these records in a file named 'AUTHORS' in the source
+ Please keep these records in a file named âAUTHORSâ in the source
directory for the program itself.
You can use the change log as the basis for these records, if you
wish. Just make sure to record the correct author for each change (the
person who wrote the change, _not_ the person who installed it), and add
-'(tiny change)' for those changes that are too trivial to matter for
-copyright purposes. Later on you can update the 'AUTHORS' file from the
+â(tiny change)â for those changes that are too trivial to matter for
+copyright purposes. Later on you can update the âAUTHORSâ file from the
change log. This can even be done 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 'AUTHORS', such as bug-reporting information. *Note
+information in âAUTHORSâ, such as bug-reporting information. *Note
Standard Mailing Lists::.
6.4 Copying from Other Packages
@@ -534,7 +534,7 @@
Here we suppose that your package is not FSF-copyrighted.
When you copy legally significant code from another free software
-package with a GPL-compatible license, you should look in the package's
+package with a GPL-compatible license, you should look in the packageâs
records to find out the authors of the part you are copying, and list
them as the contributors of the code that you copied. If all you did
was copy it, not write it, then for copyright purposes you are _not_ one
@@ -560,21 +560,21 @@
6.4.2 FSF-Copyrighted Package
-----------------------------
-If you are maintaining an FSF-copyrighted package, please don't copy in
+If you are maintaining an FSF-copyrighted package, please donât copy in
any code without verifying first that we have suitable legal papers for
that code.
If you are copying from another FSF-copyrighted package, then we
-presumably have papers for that package's own code, but you must check
+presumably have papers for that packageâs own code, but you must check
whether the code you are copying is part of an external library; if that
-is the case, we don't have papers for it, so you should not copy it. It
-can't hurt in any case to double-check with the developer of that
+is the case, we donât have papers for it, so you should not copy it. It
+canât hurt in any case to double-check with the developer of that
package.
When you are copying code for which we do not already have papers,
you need to get papers for it. It may be difficult to get the papers if
the code was not written as a contribution to your package, but that
-doesn't mean it is ok to do without them. If you cannot get papers for
+doesnât mean it is ok to do without them. If you cannot get papers for
the code, you can only use it as an external library (*note External
Libraries::).
@@ -592,7 +592,7 @@
Even image files and sound files should contain copyright notices and
license notices, if their format permits. Some formats do not have room
for textual annotations; for these files, state the copyright and
-copying permissions in a 'README' file in the same directory.
+copying permissions in a âREADMEâ file in the same directory.
Change log files should have a copyright notice and license notice at
the end, since new material is added at the beginning but the end
@@ -608,24 +608,24 @@
Copyright (C) YEAR1, YEAR2, YEAR3 COPYRIGHT-HOLDER
- The word 'Copyright' must always be in English, by international
+ The word âCopyrightâ must always be in English, by international
convention.
The COPYRIGHT-HOLDER may be the Free Software Foundation, Inc., or
someone else; you should know who is the copyright holder for your
package.
- Replace the '(C)' with a C-in-a-circle symbol if it is available.
-For example, use '@copyright{}' in a Texinfo file. However, stick with
-parenthesized 'C' unless you know that C-in-a-circle will work. For
-example, a program's standard '--version' message should use
-parenthesized 'C' by default, though message translations may use
+ Replace the â(C)â with a C-in-a-circle symbol if it is available.
+For example, use address@hidden in a Texinfo file. However, stick with
+parenthesized âCâ unless you know that C-in-a-circle will work. For
+example, a programâs standard â--versionâ message should use
+parenthesized âCâ by default, though message translations may use
C-in-a-circle in locales where that symbol is known to work.
-Alternatively, the '(C)' or C-in-a-circle can be omitted entirely; the
-word 'Copyright' suffices.
+Alternatively, the â(C)â or C-in-a-circle can be omitted entirely; the
+word âCopyrightâ suffices.
To update the list of year numbers, add each year in which you have
-made nontrivial changes to the package. (Here we assume you're using a
+made nontrivial changes to the package. (Here we assume youâre using a
publicly accessible revision control server, so that every revision
installed is also immediately and automatically published.) When you
add the new year, it is not required to keep track of which files have
@@ -633,20 +633,20 @@
recommended and simpler to add the new year to all files in the package,
and be done with it for the rest of the year.
- Don't delete old year numbers, though; they are significant since
+ Donât delete old year numbers, though; they are significant since
they indicate when older versions might theoretically go into the public
-domain, if the movie companies don't continue buying laws to further
+domain, if the movie companies donât continue buying laws to further
extend copyright. If you copy a file into the package from some other
program, keep the copyright years that come with the file.
- You can use a range ('2008-2010') instead of listing individual years
-('2008, 2009, 2010') if and only if: 1) every year in the range,
-inclusive, really is a "copyrightable" year that would be listed
-individually; _and_ 2) you make an explicit statement in a 'README' file
+ You can use a range (â2008-2010â) instead of listing individual years
+(â2008, 2009, 2010â) if and only if: 1) every year in the range,
+inclusive, really is a âcopyrightableâ year that would be listed
+individually; _and_ 2) you make an explicit statement in a âREADMEâ file
about this usage.
For files which are regularly copied from another project (such as
-'gnulib'), leave the copyright notice as it is in the original.
+âgnulibâ), leave the copyright notice as it is in the original.
The copyright statement may be split across multiple lines, both in
source files and in any generated output. This often happens for files
@@ -654,7 +654,7 @@
For an FSF-copyrighted package, if you have followed the procedures
to obtain legal papers, each file should have just one copyright holder:
-the Free Software Foundation, Inc. You should edit the file's copyright
+the Free Software Foundation, Inc. You should edit the fileâs copyright
notice to list that name and only that name.
But if contributors are not all assigning their copyrights to a
@@ -668,11 +668,11 @@
good idea for those who have contributed a large amount and for those
who specifically ask for notices in their names. (Sometimes the license
on code that you copy in may require preserving certain copyright
-notices.) But you don't have to include a notice for everyone who
+notices.) But you donât have to include a notice for everyone who
contributed to the file (which would be rather inconvenient).
Sometimes a program has an overall copyright notice that refers to
-the whole program. It might be in the 'README' file, or it might be
+the whole program. It might be in the âREADMEâ file, or it might be
displayed when the program starts up. This copyright notice should
mention the year of completion of the most recent major version; it can
mention years of completion of previous major versions, but that is
@@ -686,12 +686,12 @@
the file, the file is non-free.)
The package itself should contain a full copy of GPL in plain text
-(conventionally in a file named 'COPYING') and the GNU Free
+(conventionally in a file named âCOPYINGâ) and the GNU Free
Documentation License (included within your documentation, so there is
no need for a separate plain text version). If the package contains any
files distributed under the Lesser GPL, it should contain a full copy of
its plain text version also (conventionally in a file named
-'COPYING.LESSER').
+âCOPYING.LESSERâ).
If you have questions about licensing issues for your GNU package,
please write <address@hidden>.
@@ -700,7 +700,7 @@
-------------------------------
Normally, GNU packages should use the latest version of the GNU GPL,
-with the "or any later version" formulation. *Note License Notices for
+with the âor any later versionâ formulation. *Note License Notices for
Code::, for the exact wording of the license notice.
Occasionally, a GNU library may provide functionality which is
@@ -744,8 +744,8 @@
the GNU Lesser General Public License along with this program. If
not, see <https://www.gnu.org/licenses/>.
- For small packages, you can use "This program" instead of "GNU
-PACKAGE".
+ For small packages, you can use âThis programâ instead of âGNU
+PACKAGEâ.
6.6.2 Canonical License Sources
-------------------------------
@@ -753,9 +753,9 @@
You can get the official versions of these files from several places.
You can use whichever is the most convenient for you.
- * <https://www.gnu.org/licenses/>.
+ ⢠<https://www.gnu.org/licenses/>.
- * The 'gnulib' project on 'savannah.gnu.org', which you can access
+ ⢠The âgnulibâ project on âsavannah.gnu.orgâ, which you can access
via anonymous Git or CVS. See
<https://savannah.gnu.org/projects/gnulib>.
@@ -804,8 +804,8 @@
<https://www.gnu.org/licenses/>.
In either case, for those few packages which use the Lesser GPL
-(*note Licensing of GNU Packages::), insert the word "Lesser" before
-"General" in _all three_ places.
+(*note Licensing of GNU Packages::), insert the word âLesserâ before
+âGeneralâ in _all three_ places.
<https://www.gnu.org/licenses/gpl-howto.html> discusses application the
GPL in more detail.
@@ -831,10 +831,10 @@
If the FSF does not publish this manual on paper, then omit the last
sentence in (a) that talks about copies from GNU Press. If the FSF is
-not the copyright holder, then replace 'FSF' with the appropriate name.
+not the copyright holder, then replace âFSFâ with the appropriate name.
Please adjust the list of invariant sections as appropriate for your
-manual. If there are none, then say "with no Invariant Sections". If
+manual. If there are none, then say âwith no Invariant Sectionsâ. If
your manual is not published by the FSF, and under 400 pages, you can
omit both cover texts. However, if it is copyright FSF, always ask the
FSF what to do.
@@ -855,7 +855,7 @@
When you distribute several manuals together in one software package,
their on-line forms can share a single copy of the GFDL (see section 6).
-However, the printed ('.dvi', '.pdf', ...) forms should each contain a
+However, the printed (â.dviâ, â.pdfâ, â¦) forms should each contain a
copy of the GFDL, unless they are set up to be printed and published
only together. Therefore, it is usually simplest to include the GFDL in
each manual.
@@ -864,7 +864,7 @@
-------------------------------------
Small supporting files, short manuals (under 300 lines long) and rough
-documentation ('README' files, 'INSTALL' files, etc.) can use a simple
+documentation (âREADMEâ files, âINSTALLâ files, etc.) can use a simple
all-permissive license like this one:
Copying and distribution of this file, with or without modification,
@@ -883,7 +883,7 @@
These kinds of files can also be put in the public domain. If
publishing in the US, it is enough to insert a notice saying so.
-Otherwise, use Creative Commons's CC0--See
+Otherwise, use Creative Commonsâs CC0âSee
<https://creativecommons.org/choose/zero/>.
6.7 External Libraries
@@ -891,14 +891,14 @@
As maintainer of an FSF-copyrighted GNU package, how do you use
separately-published general-purpose free modules? (We also call them
-"libraries" because we are using them as libraries; it doesn't matter
+âlibrariesâ because we are using them as libraries; it doesnât matter
whether they are packaged as libraries or not.)
It would be unreasonable to ask their authors to assign copyright to
-the FSF. They didn't write those modules as contributions to GNU. We
+the FSF. They didnât write those modules as contributions to GNU. We
just happen to want to use them, as any developer might. It would be
rude to ask developers, out of the blue, to give the FSF their
-copyright. Please don't ask for that in cases like these.
+copyright. Please donât ask for that in cases like these.
The proper way to use those modules is to link your package with them
and say they are _not_ part of your package. See below for the
@@ -906,20 +906,20 @@
To avoid present or future legal trouble, you must make sure the
license of the module is compatible with current _and future_ GPL
-versions. "GNU GPL version 3 or later" is good, and so is anything
+versions. âGNU GPL version 3 or laterâ is good, and so is anything
which includes permission for use under those GPL versions (including
-"GNU GPL version 2 or later", "LGPL version N or later", "LGPL version
-2.1", "GNU Affero GPL version 3 or later"). Lax permissive licenses are
+âGNU GPL version 2 or laterâ, âLGPL version N or laterâ, âLGPL
version
+2.1â, âGNU Affero GPL version 3 or laterâ). Lax permissive licenses are
ok too, since they are compatible with all GPL versions.
- "GPL version 2 only" is obviously unacceptable because it is
-incompatible with GPL version 3. "GPL version 3 only" and "GPL version
-2 or 3 only" have a subtler problem: they would be incompatible with GPL
+ âGPL version 2 onlyâ is obviously unacceptable because it is
+incompatible with GPL version 3. âGPL version 3 onlyâ and âGPL version
+2 or 3 onlyâ have a subtler problem: they would be incompatible with GPL
version 4, if we ever make one, so the module would become an obstacle
-to upgrading your package's license to "GPL version 4 or later". Don't
+to upgrading your packageâs license to âGPL version 4 or laterâ. Donât
use such modules.
- One library you need to avoid is 'goffice', since it allows only GPL
+ One library you need to avoid is âgofficeâ, since it allows only GPL
versions 2 and 3.
So, here are the mechanics of how to arrange your package to use the
@@ -929,15 +929,15 @@
it when linking your program. This is only reasonable if the
module really has the form of a library.
- 2. Include the module in your package's distribution, putting the
- source in a separate subdirectory whose 'README' file says, "This
- is not part of the GNU FOO program, but is used with GNU FOO." Then
+ 2. Include the module in your packageâs distribution, putting the
+ source in a separate subdirectory whose âREADMEâ file says, âThis
+ is not part of the GNU FOO program, but is used with GNU FOO.â Then
set up your makefiles to build this module and link it into the
executable.
With this method, it is not necessary to treat the module as a
- library and make a '.a' file from it. You can link directly with
- the '.o' files in the usual manner.
+ library and make a â.aâ file from it. You can link directly with
+ the â.oâ files in the usual manner.
Both of these methods create an irregularity, and our lawyers have
told us to minimize the amount of such irregularity. So use these
@@ -953,28 +953,28 @@
In any FSF-copyrighted GNU package, the authors of a file are not
named in the copyright notice. Therefore, it is nice to include a
-comment line 'Authors: AUTHORS OF THIS FILE' at the top near the
+comment line âAuthors: AUTHORS OF THIS FILEâ at the top near the
copyright notice, to give them credit in close association with their
contribution.
7 Cleaning Up Changes
*********************
-Don't feel obligated to include every change that someone asks you to
-include. You must judge which changes are improvements--partly based on
+Donât feel obligated to include every change that someone asks you to
+include. You must judge which changes are improvementsâpartly based on
what you think the users will like, and partly based on your own
judgment of what is better. If you think a change is not good, you
should reject it.
If someone sends you changes which are useful, but written in an ugly
-way or hard to understand and maintain in the future, don't hesitate to
+way or hard to understand and maintain in the future, donât hesitate to
ask per to clean up their changes before you merge them. Since the
amount of work we can do is limited, the more we convince others to help
us work efficiently, the faster GNU will advance.
If the contributor will not or can not make the changes clean enough,
-then it is legitimate to say "I can't install this in its present form;
-I can only do so if you clean it up." Invite per to distribute per
+then it is legitimate to say âI canât install this in its present form;
+I can only do so if you clean it up.â Invite per to distribute per
changes another way, or to find other people to make them clean enough
for you to install and maintain.
@@ -1007,9 +1007,9 @@
You will naturally want to keep the program running on all the
platforms it supports. But you personally will not have access to most
-of these platforms--so how should you do it?
+of these platformsâso how should you do it?
- Don't worry about trying to get access to all of these platforms.
+ Donât worry about trying to get access to all of these platforms.
Even if you did have access to all the platforms, it would be
inefficient for you to test the program on each platform yourself.
Instead, you should test the program on a few platforms, including GNU
@@ -1021,16 +1021,16 @@
It is important to test the program personally on GNU or GNU/Linux,
because these are the most important platforms for a GNU package. If
-you don't have access to one of these platforms, as a GNU maintainer you
+you donât have access to one of these platforms, as a GNU maintainer you
can get access to the general GNU login machine; see
<https://www.gnu.org/software/README.accounts.html>.
- Supporting other platforms is optional--we do it when that seems like
-a good idea, but we don't consider it obligatory. If the users don't
+ Supporting other platforms is optionalâwe do it when that seems like
+a good idea, but we donât consider it obligatory. If the users donât
take care of a certain platform, you may have to desupport it unless and
until users come forward to help. Conversely, if a user offers changes
to support an additional platform, you will probably want to install
-them, but you don't have to. If you feel the changes are complex and
+them, but you donât have to. If you feel the changes are complex and
ugly, if you think that they will increase the burden of future
maintenance, you can and should reject them. This includes both free or
mainly-free platforms such as OpenBSD, FreeBSD, and NetBSD, and non-free
@@ -1049,12 +1049,12 @@
Once a program is in use, you will get bug reports for it. Most GNU
programs have their own special lists for sending bug reports. The
advertised bug-reporting email address should always be
-'address@hidden', to help show users that the program is a GNU
address@hidden, 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.
We also have a catch-all list, <address@hidden>, which is used
-for all GNU programs that don't have their own specific lists. But
+for all GNU programs that donât have their own specific lists. But
nowadays we want to give each program its own bug-reporting list and
move away from using <bug-gnu-utils>.
@@ -1062,46 +1062,46 @@
reports.
Some GNU programs with many users have another mailing list,
-'address@hidden', for people to ask other users for help. If your
address@hidden, for people to ask other users for help. If your
program has many users, you should create such a list for it. For a
-fairly new program, which doesn't have a large user base yet, it is
+fairly new program, which doesnât have a large user base yet, it is
better not to bother with this.
- If you wish, you can also have a mailing list 'address@hidden'
+ If you wish, you can also have a mailing list address@hidden
for announcements (*note Announcements::). Any other mailing lists you
find useful can also be created.
- The package distribution should state the name of all the package's
+ 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 'README' file and/or
-'AUTHORS' file are good places. Mailing list information should also be
+reporting bugs appropriately. The top-level âREADMEâ file and/or
+âAUTHORSâ file are good places. Mailing list information should also be
included in the manual and the package web pages (*note Web Pages::).
9.2 Creating Mailing Lists
==========================
-Using the web interface on 'savannah.gnu.org' is by far the easiest way
+Using the web interface on âsavannah.gnu.orgâ is by far the easiest way
to create normal mailing lists, managed through Mailman on the GNU mail
server. Once you register your package on Savannah, you can create (and
-remove) lists yourself through the 'Mailing Lists' menu, without needing
+remove) lists yourself through the âMailing Listsâ menu, without needing
to wait for intervention by anyone else. Furthermore, lists created
through Savannah will have a reasonable default configuration for
antispam purposes (see below).
To create and maintain simple aliases and unmanaged lists, you can
-edit '/com/mailer/aliases' on the main GNU server. If you don't have an
+edit â/com/mailer/aliasesâ on the main GNU server. If you donât have an
account there, please read
<https://www.gnu.org/software/README.accounts.html> (*note GNU Accounts
and Resources::).
- But if you don't want to learn how to do those things, you can ask
+ But if you donât want to learn how to do those things, you can ask
<address@hidden> to help you.
You should moderate postings from non-subscribed addresses on your
-mailing lists, to prevent propagation of unwanted messages ("spam") to
+mailing lists, to prevent propagation of unwanted messages (âspamâ) to
subscribers and to the list archives. For lists controlled by Mailman,
-you can do this by setting 'Privacy Options - Sender Filter -
-generic_nonmember_action' to 'Hold', and then periodically (daily is
+you can do this by setting âPrivacy Options - Sender Filter -
+generic_nonmember_actionâ to âHoldâ, and then periodically (daily is
best) reviewing the held messages, accepting the real ones and
discarding the junk.
@@ -1115,36 +1115,35 @@
====================
When you receive bug reports, keep in mind that bug reports are crucial
-for your work. If you don't know about problems, you cannot fix them.
+for your work. If you donât know about problems, you cannot fix them.
So always thank each person who sends a bug report.
- You don't have an obligation to give more response than that, though.
+ You donât have an obligation to give more response than that, though.
The main purpose of bug reports is to help you contribute to the
community by improving the next version of the program. Many of the
-people who report bugs don't realize this--they think that the point is
+people who report bugs donât realize thisâthey think that the point is
for you to help them individually. Some will ask you to focus on that
_instead of_ on making the program better. If you comply with their
wishes, you will have been distracted from the job of maintaining the
program.
For example, people sometimes report a bug in a vague (and therefore
-useless) way, and when you ask for more information, they say, "I just
-wanted to see if you already knew the solution" (in which case the bug
+useless) way, and when you ask for more information, they say, âI just
+wanted to see if you already knew the solutionâ (in which case the bug
report would do nothing to help improve the program). When this
happens, you should explain to them the real purpose of bug reports. (A
canned explanation will make this more efficient.)
When people ask you to put your time into helping them use the
-program, it may seem "helpful" to do what they ask. But it is much
-_less_ helpful than improving the program, which is the maintainer's
+program, it may seem âhelpfulâ to do what they ask. But it is much
+_less_ helpful than improving the program, which is the maintainerâs
real job.
By all means help individual users when you feel like it, if you feel
you have the time available. But be careful to limit the amount of time
-you spend doing this--don't let it eat away the time you need to
-maintain the program! Know how to say no; when you are pressed for
-time, just "thanks for the bug report--I will fix it" is enough
-response.
+you spend doing thisâdonât let it eat away the time you need to maintain
+the program! Know how to say no; when you are pressed for time, just
+âthanks for the bug reportâI will fix itâ is enough response.
Some GNU packages, such as Emacs and GCC, come with advice about how
to make bug reports useful. Copying and adapting that could be very
@@ -1154,8 +1153,8 @@
<https://bugs.gnu.org>; this can be connected with the regular
bug-reporting address. Alternatively, if you would like to use a
web-based bug tracking system, Savannah supports this (*note Old
-Versions::), but please don't fail to accept bugs by regular email as
-well--we don't want to put up unnecessary barriers against users
+Versions::), but please donât fail to accept bugs by regular email as
+wellâwe donât want to put up unnecessary barriers against users
submitting reports.
10 Recording Old Versions
@@ -1163,7 +1162,7 @@
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, ...) if you like. An easy way to use many such systems
+Git, Subversion, â¦) if you like. An easy way to use many such systems
is via the Version Control library in Emacs (*note Introduction to
Version Control: (emacs)Introduction to VC.).
@@ -1174,15 +1173,15 @@
some day.
The GNU Project provides a server that GNU packages can use for
-source control and other package needs: 'savannah.gnu.org'. Savannah is
+source control and other package needs: âsavannah.gnu.orgâ. Savannah is
managed by <address@hidden>. For more details on using and
contributing to Savannah, see <https://savannah.gnu.org/maintenance>.
- It's not an absolute requirement, but all GNU maintainers are
+ 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 as well as help in keeping up with project management.
-Please don't mark Savannah projects for GNU packages as private; that
+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.
@@ -1202,13 +1201,13 @@
===========================
All packages should provide tar files for the distribution of their
-releases. The tar file for version M.N of program 'foo' should be named
-'foo-M.N.tar'. It should unpack into a subdirectory named 'foo-M.N'.
+releases. The tar file for version M.N of program âfooâ should be named
+âfoo-M.N.tarâ. It should unpack into a subdirectory named âfoo-M.Nâ.
Tar files should not unpack into files in the current directory, because
this is inconvenient if the user happens to unpack into a directory with
other files in it.
- Here is how the 'Makefile' for Bison creates the tar file. This
+ Here is how the âMakefileâ for Bison creates the tar file. This
method is good for other programs.
dist: bison.info
@@ -1224,10 +1223,10 @@
-rm -rf `cat .fname` .fname
Source files that are symbolic links to other file systems cannot be
-installed in the temporary directory using 'ln', so use 'cp' if 'ln'
+installed in the temporary directory using âlnâ, so use âcpâ if
âlnâ
fails.
- Using Automake is a good way to take care of writing the 'dist'
+ Using Automake is a good way to take care of writing the âdistâ
target.
11.2 Distribution Patches
@@ -1248,14 +1247,14 @@
the installer to recompile the patched sources.
When you make the diffs, each version should be in a directory
-suitably named--for example, 'gcc-2.3.2' and 'gcc-2.3.3'. This way, it
+suitably namedâfor example, âgcc-2.3.2â and âgcc-2.3.3â. This way,
it
will be very clear from the diffs themselves which version is which.
- If you use GNU 'diff' to make the patch, use the options '-rc2P'.
-That will put any new files into the output as "entirely different".
-Also, the patch's context diff headers should have dates and times in
+ If you use GNU âdiffâ to make the patch, use the options â-rc2Pâ.
+That will put any new files into the output as âentirely differentâ.
+Also, the patchâs context diff headers should have dates and times in
Universal Time using traditional Unix format, so that patch recipients
-can use GNU 'patch''s '-Z' option. For example, you could use the
+can use GNU âpatchââs â-Zâ option. For example, you could use the
following Bourne shell command to create the patch:
LC_ALL=C TZ=UTC0 diff -rc2P gcc-2.3.2 gcc-2.3.3 | \
@@ -1267,18 +1266,18 @@
For example, say this:
To apply these patches, cd to the main directory of the program
- and then use 'patch -p1'. '-p1' avoids guesswork in choosing
+ and then use âpatch -p1â. â-p1â avoids guesswork in choosing
which subdirectory to find each file in.
- It's wise to test your patch by applying it to a copy of the old
+ Itâs wise to test your patch by applying it to a copy of the old
version, and checking that the result exactly matches the new version.
11.3 Binary Distribution for Nonfree Platforms
==============================================
Some package maintainers release pre-compiled binaries for proprietary
-systems such as Microsoft Windows or MacOS. It's entirely up to you
-whether to do that; we don't ask you to do it, but we don't object.
+systems such as Microsoft Windows or MacOS. Itâs entirely up to you
+whether to do that; we donât ask you to do it, but we donât object.
Please do not let anyone make you feel you have an obligation to do
this.
@@ -1286,20 +1285,20 @@
those non-free platforms trample their freedom. It is useful to refer
them to
<https://www.gnu.org/philosophy/free-software-even-more-important.html>.
-You can say, "This program respects your freedom, but Windows does not.
+You can say, âThis program respects your freedom, but Windows does not.
To have freedom, you need to stop using Windows and other software that
-denies your freedom."
+denies your freedom.â
-11.4 Distribution on 'ftp.gnu.org'
+11.4 Distribution on âftp.gnu.orgâ
==================================
-We strongly recommend using 'ftp.gnu.org' to distribute official
+We strongly recommend using âftp.gnu.orgâ to distribute official
releases. If you want to also distribute the package from a site of
-your own, that is fine. To use some other site instead of 'ftp.gnu.org'
+your own, that is fine. To use some other site instead of âftp.gnu.orgâ
is acceptable, provided it allows connections from anyone anywhere.
*Note Automated FTP Uploads::, for the procedural details of putting
-new versions on 'ftp.gnu.org'.
+new versions on âftp.gnu.orgâ.
11.5 Test Releases
==================
@@ -1309,12 +1308,12 @@
but send it only to a group of volunteers that you have recruited. (Use
a suitable GNU mailing list/newsgroup to recruit them.)
- We normally use the server 'alpha.gnu.org' for pretests and
+ We normally use the server âalpha.gnu.orgâ for pretests and
prerelease versions. *Note Automated FTP Uploads::, for the procedural
-details of putting new versions on 'alpha.gnu.org'.
+details of putting new versions on âalpha.gnu.orgâ.
Once a program gets to be widely used and people expect it to work
-solidly, it is a good idea to do pretest releases before each "real"
+solidly, it is a good idea to do pretest releases before each ârealâ
release.
There are three ways of handling version numbers for pretest
@@ -1337,9 +1336,9 @@
the date without the version numbers is ok too.
A third method, if the package uses Git, is to run the script
-'build-aux/git-version-gen' from Gnulib to generate test release version
+âbuild-aux/git-version-genâ from Gnulib to generate test release version
numbers. It generates version numbers in the form
-'VERSION.COMMITS-COMMITHASH', where VERSION is the latest version tag,
+âVERSION.COMMITS-COMMITHASHâ, where VERSION is the latest version tag,
COMMITS is the number of commits since that tag, and COMMITHASH is a
hash code for the latest commit.
@@ -1354,7 +1353,7 @@
11.6 Automated FTP Uploads
==========================
-In order to upload new releases to 'ftp.gnu.org' or 'alpha.gnu.org', you
+In order to upload new releases to âftp.gnu.orgâ or âalpha.gnu.orgâ,
you
first need to register the necessary information. Then, you can perform
uploads yourself, with no intervention needed by the system
administrators.
@@ -1369,26 +1368,26 @@
your GNU package:
1. Create an account for yourself at <https://savannah.gnu.org>, if
- you don't already have one. By the way, this is also needed to
+ you donât already have one. By the way, this is also needed to
maintain the web pages at <https://www.gnu.org> for your project
(*note Web Pages::).
- 2. In the 'My Account Conf' page on 'savannah', upload the GPG key (in
+ 2. In the âMy Account Confâ page on âsavannahâ, upload the GPG key
(in
ASCII-armored format) that you will use to sign your packages. If
- you haven't created one before, you can do so with the command 'gpg
- --gen-key' (you can accept and/or confirm the default answers to
- its questions). Then, to get the ASCII-armored version, run 'gpg
- --export --armor YOUR_KEY_ID'.
+ you havenât created one before, you can do so with the command âgpg
+ --gen-keyâ (you can accept and/or confirm the default answers to
+ its questions). Then, to get the ASCII-armored version, run âgpg
+ --export --armor YOUR_KEY_IDâ.
Optional but recommended: Send your key to a GPG public key server:
- 'gpg --keyserver keys.gnupg.net --send-keys KEYID', where KEYID is
- the eight hex digits reported by 'gpg --list-public-keys' on the
- 'pub' line before the date. For full information about GPG, see
+ âgpg --keyserver keys.gnupg.net --send-keys KEYIDâ, where KEYID is
+ the eight hex digits reported by âgpg --list-public-keysâ on the
+ âpubâ line before the date. For full information about GPG, see
<https://www.gnu.org/software/gpg>.
3. Compose a message with the following items in some MSGFILE. Then
- GPG-sign it by running 'gpg --clearsign MSGFILE', and finally email
- the resulting 'MSGFILE.asc' to <address@hidden>.
+ GPG-sign it by running âgpg --clearsign MSGFILEâ, and finally email
+ the resulting âMSGFILE.ascâ to <address@hidden>.
1. Name of package(s) that you are the maintainer for, your
preferred email address, and your Savannah username.
@@ -1397,7 +1396,7 @@
3. A list of names and preferred email addresses of other
individuals you authorize to make releases for which packages,
- if any (in the case that you don't make all releases
+ if any (in the case that you donât make all releases
yourself).
4. ASCII armored copies of GPG keys for any individuals listed in
@@ -1410,7 +1409,7 @@
The upload system will email receipts to the given email addresses
when an upload is made, either successfully or unsuccessfully.
- Should you later have to update your GPG key, you'll have to
+ Should you later have to update your GPG key, youâll have to
re-submit it to both Savannah and <address@hidden>, as these systems
are not connected.
@@ -1421,18 +1420,18 @@
section, you can and should do ftp uploads for your package. There are
two basic kinds of uploads (details in the following sections):
- 1. Three related files (a "triplet") to upload a file destined for
- 'ftp.gnu.org' or 'alpha.gnu.org': *note FTP Upload Release File
+ 1. Three related files (a âtripletâ) to upload a file destined for
+ âftp.gnu.orgâ or âalpha.gnu.orgâ: *note FTP Upload Release File
Triplet::.
- 2. A single (signed) standalone "directive file" to perform operations
+ 2. A single (signed) standalone âdirective fileâ to perform operations
on the server: *note FTP Upload Standalone Directives::.
In either case, you upload the file(s) via anonymous ftp to the host
-'ftp-upload.gnu.org'. If the upload is destined for 'ftp.gnu.org',
-place the file(s) in the directory '/incoming/ftp'. If the upload is
-destined for 'alpha.gnu.org', place the file(s) in the directory
-'/incoming/alpha'.
+âftp-upload.gnu.orgâ. If the upload is destined for âftp.gnu.orgâ,
+place the file(s) in the directory â/incoming/ftpâ. If the upload is
+destined for âalpha.gnu.orgâ, place the file(s) in the directory
+â/incoming/alphaâ.
Uploads are processed every five minutes. Uploads that are in
progress while the upload processing script is running are handled
@@ -1445,17 +1444,17 @@
been successfully processed.
One programmatic way to create and transfer the necessary files is to
-use the 'gnupload' script, which is available from the 'build-aux/'
-directory of the 'gnulib' project at
-<https://savannah.gnu.org/projects/gnulib>. Run 'gnupload --help' for a
-description and examples. (With 'gnupload', you specify a destination
-such as 'ftp.gnu.org:'PKGNAME rather than using the 'ftp-upload'
+use the âgnuploadâ script, which is available from the âbuild-aux/â
+directory of the âgnulibâ project at
+<https://savannah.gnu.org/projects/gnulib>. Run âgnupload --helpâ for a
+description and examples. (With âgnuploadâ, you specify a destination
+such as âftp.gnu.org:âPKGNAME rather than using the âftp-uploadâ
hostname.)
- 'gnupload' invokes the program 'ncftpput' to do the actual transfers;
-if you don't happen to have the 'ncftp' package installed, the
-'ncftpput-ftp' script in the 'build-aux/' directory of 'gnulib' can
-serve as a replacement. It uses the plain command line 'ftp' program.
+ âgnuploadâ invokes the program âncftpputâ to do the actual
transfers;
+if you donât happen to have the âncftpâ package installed, the
+âncftpput-ftpâ script in the âbuild-aux/â directory of âgnulibâ can
+serve as a replacement. It uses the plain command line âftpâ program.
If you have difficulties with an upload, email <address@hidden>.
You can check the archive of uploads processed at
@@ -1464,24 +1463,24 @@
11.6.3 FTP Upload Release File Triplet
--------------------------------------
-Ordinarily, the goal is to upload a new release of your package, let's
-say, the source archive 'foo-1.0.tar.gz'. To do this, you
+Ordinarily, the goal is to upload a new release of your package, letâs
+say, the source archive âfoo-1.0.tar.gzâ. To do this, you
simultaneously upload three files:
- 1. The file to be distributed; in our example, 'foo-1.0.tar.gz'.
+ 1. The file to be distributed; in our example, âfoo-1.0.tar.gzâ.
2. Detached GPG binary signature file for (1); for example,
- 'foo-1.0.tar.gz.sig'. Make this with 'gpg -b foo-1.0.tar.gz'.
+ âfoo-1.0.tar.gz.sigâ. Make this with âgpg -b foo-1.0.tar.gzâ.
3. A clearsigned "directive file"; for example,
- 'foo-1.0.tar.gz.directive.asc', created with 'gpg --clearsign
- foo-1.0.tar.gz.directive'. Its contents are described in the next
+ âfoo-1.0.tar.gz.directive.ascâ, created with âgpg --clearsign
+ foo-1.0.tar.gz.directiveâ. Its contents are described in the next
section.
The names of the files are important. The signature file must have
-the same name as the file to be distributed, with an additional '.sig'
+the same name as the file to be distributed, with an additional â.sigâ
extension. The directive file must have the same name as the file to be
-distributed, with an additional '.directive.asc' extension. If you do
+distributed, with an additional â.directive.ascâ extension. If you do
not follow this naming convention, the upload _will not be processed_.
11.6.4 FTP Upload Directive File
@@ -1489,64 +1488,64 @@
To repeat, a (signed) "directive file" must be part of every upload.
The unsigned original is just a plain text file you can create with any
-text editor. Its name must be, e.g., 'foo-1.0.tar.gz.directive' for
-accompanying an upload of 'foo-1.0.tar.gz'.
+text editor. Its name must be, e.g., âfoo-1.0.tar.gz.directiveâ for
+accompanying an upload of âfoo-1.0.tar.gzâ.
- After creating the file, run 'gpg --clearsign
-foo-1.0.tar.gz.directive', which will create
-'foo-1.0.tar.gz.directive.asc'; this is the file to be uploaded.
+ After creating the file, run âgpg --clearsign
+foo-1.0.tar.gz.directiveâ, which will create
+âfoo-1.0.tar.gz.directive.ascâ; this is the file to be uploaded.
When part of a triplet for uploading a release file, the directive
-file must always contain the directives 'version', 'filename' and
-'directory'. In addition, a 'comment' directive is optional. These
+file must always contain the directives âversionâ, âfilenameâ and
+âdirectoryâ. In addition, a âcommentâ directive is optional. These
directives can be given in any order.
- Continuing our example of uploading 'foo-1.0.tar.gz' for a package
-named 'foo' to 'ftp.gnu.org', the values would be as follows:
+ Continuing our example of uploading âfoo-1.0.tar.gzâ for a package
+named âfooâ to âftp.gnu.orgâ, the values would be as follows:
-'version'
- must be the value '1.2' (the current version, as of May 2012):
+âversionâ
+ must be the value â1.2â (the current version, as of May 2012):
version: 1.2
-'filename'
+âfilenameâ
must be the name of the file to be distributed:
filename: foo-1.0.tar.gz
-'directory'
+âdirectoryâ
specifies the final destination directory where the uploaded file
- and its '.sig' companion are to be placed. Here we will put our
+ and its â.sigâ companion are to be placed. Here we will put our
file in the top level directory of the package, as is the most
common practice:
directory: foo
-'comment'
+âcommentâ
is optional, and ignored if present:
comment: let's hope this works!
Putting all of the above together, the complete contents of the
-directive file 'foo-1.0.tar.gz.directive' for our example would be:
+directive file âfoo-1.0.tar.gz.directiveâ for our example would be:
version: 1.2
directory: foo
filename: foo-1.0.tar.gz
comment: let's hope this works!
- Then you 'gpg --clearsign' the file as given above, and upload (using
+ Then you âgpg --clearsignâ the file as given above, and upload (using
anonymous ftp) the three files:
-'foo-1.0.tar.gz'
-'foo-1.0.tar.gz.sig'
-'foo-1.0.tar.gz.directive.asc'
+âfoo-1.0.tar.gzâ
+âfoo-1.0.tar.gz.sigâ
+âfoo-1.0.tar.gz.directive.ascâ
-to the host 'ftp-upload.gnu.org', directory '/incoming/ftp' (for
-official releases), or the directory '/incoming/alpha' (for test
+to the host âftp-upload.gnu.orgâ, directory â/incoming/ftpâ (for
+official releases), or the directory â/incoming/alphaâ (for test
releases).
After the system authenticates the signatures, the files
-'foo-1.0.tar.gz' and 'foo-1.0.tar.gz.sig' are placed in the directory
-'gnu/foo/' on 'ftp.gnu.org'. That is, we'll have made our release
-available at 'https://ftp.gnu.org/gnu/foo/foo-1.0.tar.gz' (and then from
-our many mirrors via 'https://ftpmirror.gnu.org/foo/foo-1.0.tar.gz').
+âfoo-1.0.tar.gzâ and âfoo-1.0.tar.gz.sigâ are placed in the directory
+âgnu/foo/â on âftp.gnu.orgâ. That is, weâll have made our release
+available at âhttps://ftp.gnu.org/gnu/foo/foo-1.0.tar.gzâ (and then from
+our many mirrors via âhttps://ftpmirror.gnu.org/foo/foo-1.0.tar.gzâ).
Whew.
A common reason for the upload not succeeding is your GPG signature
@@ -1560,7 +1559,7 @@
You can make any directory hierarchy you like under your package
directory. The system automatically creates any intermediate
-directories you specify in the 'directory' directive.
+directories you specify in the âdirectoryâ directive.
Slightly modifying the example above, the following directive file:
@@ -1569,8 +1568,8 @@
filename: foo-1.0.tar.gz
comment: creates per-version subdirectory as needed
-would put the tar file in the 'foo-1.0/' subdirectory of the package
-'foo', thus ending up at 'ftp.gnu.org:gnu/foo/foo-1.0/foo-1.0.tar.gz'.
+would put the tar file in the âfoo-1.0/â subdirectory of the package
+âfooâ, thus ending up at âftp.gnu.org:gnu/foo/foo-1.0/foo-1.0.tar.gzâ.
However, to keep things simpler for users, we recommend not using
subdirectories, unless perhaps each release of your package consists of
@@ -1580,7 +1579,7 @@
----------------------------------
You can replace existing files that have already been uploaded by
-including a directive line 'replace: true'. For example, you might like
+including a directive line âreplace: trueâ. For example, you might like
to provide a README file in the release directory and update it from
time to time. The full directive file for that would look like this:
@@ -1590,8 +1589,8 @@
filename: README
comment: replaces an existing README
- It is ok if the file to be replaced doesn't already exist; then the
-new file is simply added, i.e., the 'replace' directive has no effect.
+ It is ok if the file to be replaced doesnât already exist; then the
+new file is simply added, i.e., the âreplaceâ directive has no effect.
When an existing file is replaced, the original is archived to a
private location. There is no automated or public access to such
@@ -1599,46 +1598,46 @@
<address@hidden>.
We very strongly discourage replacing an actual software release
-file, such as 'foo-1.0.tar.gz'. Releases should be unique, and forever.
+file, such as âfoo-1.0.tar.gzâ. Releases should be unique, and forever.
If you need to make fixes, make another release. If you have an exigent
reason for a particular release file to no longer be available, it can
be explicitly archived, as described in the next section.
If you want to make the current release available under a generic
-name, such as 'foo-latest.tar.gz', that is better done with symlinks,
+name, such as âfoo-latest.tar.gzâ, that is better done with symlinks,
also as described in the next section.
11.6.7 FTP Upload Standalone Directives
---------------------------------------
The previous sections describe how to upload a file to be publicly
-released. It's also possible to upload a directive file by itself to
+released. Itâs also possible to upload a directive file by itself to
perform a few operations on the upload directory. The supported
directives are:
-'symlink'
+âsymlinkâ
creates a symlink.
-'rmsymlink'
+ârmsymlinkâ
removes a symlink.
-'archive'
+âarchiveâ
takes a file or directory offline.
- As for the directives described above, the 'directory' and 'version'
-directives are still required, the 'comment' directive remains optional,
-and the 'filename' directive is not allowed.
+ As for the directives described above, the âdirectoryâ and âversionâ
+directives are still required, the âcommentâ directive remains optional,
+and the âfilenameâ directive is not allowed.
- The '.sig' file should not be explicitly mentioned in a directive.
+ The â.sigâ file should not be explicitly mentioned in a directive.
When you specify a directive to operate on a file, its corresponding
-'.sig' file will be handled automatically.
+â.sigâ file will be handled automatically.
When uploaded by itself, the name of the directive file is not
-important. But it must be still be signed, using 'gpg --clearsign'; the
-resulting '.asc' file is what should be uploaded.
+important. But it must be still be signed, using âgpg --clearsignâ; the
+resulting â.ascâ file is what should be uploaded.
- Here's an example of the full directive file to create a
-'foo-latest.tar.gz' symlink:
+ Hereâs an example of the full directive file to create a
+âfoo-latest.tar.gzâ symlink:
version: 1.2
directory: foo
@@ -1650,22 +1649,22 @@
directive results in an error, further execution of the upload is
aborted.
- Removing a symbolic link (with 'rmsymlink') which does not exist
+ Removing a symbolic link (with ârmsymlinkâ) which does not exist
results in an error. On the other hand, attempting to create a symbolic
-link that already exists (with 'symlink') is not an error. In this case
-'symlink' behaves like the command 'ln -s -f': any existing symlink is
+link that already exists (with âsymlinkâ) is not an error. In this case
+âsymlinkâ behaves like the command âln -s -fâ: any existing symlink is
removed before creating the link. (But an existing regular file or
directory is not replaced.)
- Here's an example of removing a symlink, e.g., if you decide not to
-maintain a 'foo-latest' link any more:
+ Hereâs an example of removing a symlink, e.g., if you decide not to
+maintain a âfoo-latestâ link any more:
version: 1.2
directory: foo
rmsymlink: foo-latest.tar.gz
comment: remove a symlink
-And here's an example of archiving a file, e.g., an unintended upload:
+And hereâs an example of archiving a file, e.g., an unintended upload:
version: 1.2
directory: foo
@@ -1673,20 +1672,20 @@
comment: archive an old file; it will not be
comment: publicly available any more.
- The 'archive' directive causes the specified items to become
+ The âarchiveâ directive causes the specified items to become
inaccessible. This should only be used when it is actively bad for them
to be available, e.g., you uploaded something by mistake.
If all you want to do is reduce how much stuff is in your release
directory, an alternative is to email <address@hidden> and ask them to
-move old items to the 'https://ftp.gnu.org/old-gnu/' directory; then
+move old items to the âhttps://ftp.gnu.org/old-gnu/â directory; then
they will still be available. In general, however, we recommend leaving
all official releases in the main release directory.
11.6.8 FTP Upload Directive File - v1.1
---------------------------------------
-The v1.1 protocol for uploads lacked the 'replace' directive; instead,
+The v1.1 protocol for uploads lacked the âreplaceâ directive; instead,
file replacements were done automatically and silently (clearly
undesirable). This is the only difference between v1.2 and v1.1.
@@ -1700,21 +1699,21 @@
clearsigned data GPG that inserts, which specifies the final destination
directory where items (1) and (2) are to be placed.
- For example, the 'foo-1.0.tar.gz.directive.asc' file might contain
+ For example, the âfoo-1.0.tar.gz.directive.ascâ file might contain
the single line:
directory: bar/v1
- This directory line indicates that 'foo-1.0.tar.gz' and
-'foo-1.0.tar.gz.sig' are part of package 'bar'. If you were to upload
-the triplet to '/incoming/ftp', and the system can positively
-authenticate the signatures, then the files 'foo-1.0.tar.gz' and
-'foo-1.0.tar.gz.sig' will be placed in the directory 'gnu/bar/v1' of the
-'ftp.gnu.org' site.
+ This directory line indicates that âfoo-1.0.tar.gzâ and
+âfoo-1.0.tar.gz.sigâ are part of package âbarâ. If you were to upload
+the triplet to â/incoming/ftpâ, and the system can positively
+authenticate the signatures, then the files âfoo-1.0.tar.gzâ and
+âfoo-1.0.tar.gz.sigâ will be placed in the directory âgnu/bar/v1â of
the
+âftp.gnu.orgâ site.
The directive file can be used to create currently non-existent
directory trees, as long as they are under the package directory for
-your package (in the example above, that is 'bar').
+your package (in the example above, that is âbarâ).
11.7 Announcing Releases
========================
@@ -1724,7 +1723,7 @@
recommend using the (moderated) general GNU announcements list,
<address@hidden>. Doing so makes it easier for users and developers
to find the latest GNU releases. On the other hand, please do not
-announce test releases on 'info-gnu' unless it's a highly unusual
+announce test releases on âinfo-gnuâ unless itâs a highly unusual
situation.
Please also post release announcements in the news section of your
@@ -1732,50 +1731,50 @@
test releases and any other newsworthy events. The news feeds from all
GNU projects at savannah are aggregated at <https://planet.gnu.org> (GNU
Planet), unless the text of the entry contains the string
-'::noplanet::'. You can also post items directly, or arrange for feeds
+â::noplanet::â. You can also post items directly, or arrange for feeds
from other locations; see information on the GNU Planet web page.
You can maintain your own mailing list (typically
-'address@hidden') for announcements as well if you like. For your
address@hidden) for announcements as well if you like. For your
own list, of course you decide as you see fit what events are worth
announcing. (*Note Mail::, for setting this up, and more suggestions on
handling mail for your package.)
When writing an announcement, please include the following:
- * A very brief description (a few sentences at most) of the general
+ ⢠A very brief description (a few sentences at most) of the general
purpose of your package.
- * Your package's web page (normally
- 'https://www.gnu.org/software/PACKAGE/').
+ ⢠Your packageâs web page (normally
+ âhttps://www.gnu.org/software/PACKAGE/â).
- * Your package's download location (normally
- 'https://ftp.gnu.org/gnu/PACKAGE/'). It is also useful to mention
+ ⢠Your packageâs download location (normally
+ âhttps://ftp.gnu.org/gnu/PACKAGE/â). It is also useful to mention
the mirror list at <https://www.gnu.org/order/ftp.html>, and that
- 'https://ftpmirror.gnu.org/PACKAGE/' will automatically redirect to
+ âhttps://ftpmirror.gnu.org/PACKAGE/â will automatically redirect to
a nearby mirror.
- * The NEWS (*note (standards)NEWS File::) for the present release.
+ ⢠The NEWS (*note (standards)NEWS File::) for the present release.
- You may find the 'announce-gen' script useful for creating
-announcements, which is available from the 'build-aux/' directory of the
-'gnulib' project at <https://savannah.gnu.org/projects/gnulib>.
+ You may find the âannounce-genâ script useful for creating
+announcements, which is available from the âbuild-aux/â directory of the
+âgnulibâ project at <https://savannah.gnu.org/projects/gnulib>.
12 Web Pages
************
As soon as a new package is dubbed GNU, its home page
-('https://www.gnu.org/software/PACKAGE/') is listed on
+(âhttps://www.gnu.org/software/PACKAGE/â) is listed on
<https://www.gnu.org/software/software.html> and
<https://www.gnu.org/manual/manual.html>. To avoid broken links, the
webmasters create a temporary home page as follows:
- * If there is a Savannah project for this package (*note Hosting for
- Web Pages::), the temporary home page redirects to the project's
- main page, 'https://savannah.gnu.org/projects/PACKAGE', where a
+ ⢠If there is a Savannah project for this package (*note Hosting for
+ Web Pages::), the temporary home page redirects to the projectâs
+ main page, âhttps://savannah.gnu.org/projects/PACKAGEâ, where a
short description should be available.
- * Otherwise, the webmasters make a simple home page containing the
+ ⢠Otherwise, the webmasters make a simple home page containing the
short description provided with the original submission of the
package to GNU.
@@ -1784,10 +1783,10 @@
Some GNU packages have just simple web pages, but the more
information you provide, the better. So please write as much as you
-usefully can, and put all of it on 'www.gnu.org'. However, pages that
+usefully can, and put all of it on âwww.gnu.orgâ. However, pages that
access databases (including mail archives and bug tracking) are an
exception; set them up on whatever site is convenient for you, and make
-the pages on 'www.gnu.org' link to that site.
+the pages on âwww.gnu.orgâ link to that site.
Your web pages should follow our usual standards (see
<https://www.gnu.org/server/fsf-html-style-sheet.html>). The overall
@@ -1795,7 +1794,7 @@
rather than visual adornments, and to keep gnu.org/software/ consistent
on certain important points.
- We encourage you to use the standard 'www.gnu.org' template as the
+ We encourage you to use the standard âwww.gnu.orgâ template as the
basis for your pages:
<https://www.gnu.org/server/standards/boilerplate-source.html>. This
template changes slightly from time to time for various reasons. If a
@@ -1809,14 +1808,14 @@
==========================
The best way to maintain the web pages for your project is to register
-the project on 'savannah.gnu.org'. Then you can edit the pages using
-CVS, using the separate "web pages repository" available on Savannah,
-which corresponds to 'https://www.gnu.org/software/PACKAGE/'. You can
+the project on âsavannah.gnu.orgâ. Then you can edit the pages using
+CVS, using the separate âweb pages repositoryâ available on Savannah,
+which corresponds to âhttps://www.gnu.org/software/PACKAGE/â. You can
keep your source files there too (using any of a variety of version
-control systems), but you can use 'savannah.gnu.org' only for your
-gnu.org web pages if you wish; simply register a "web-only" project.
+control systems), but you can use âsavannah.gnu.orgâ only for your
+gnu.org web pages if you wish; simply register a âweb-onlyâ project.
- If you don't want to use that method, please talk with
+ If you donât want to use that method, please talk with
<address@hidden> about other possible methods. For instance, you
can mail them pages to install, if necessary. But that is more work for
them, so please use Savannah if you can.
@@ -1825,7 +1824,7 @@
web pages (HTML, CSS, obvious typos, broken links in the footer, etc.)
and inform you of the change afterwards.
- If you use Savannah, you can use a special file named '.symlinks' in
+ If you use Savannah, you can use a special file named â.symlinksâ in
order to create symbolic links, which are not supported in CVS. For
details, see
<https://www.gnu.org/server/standards/README.webmastering.html#symlinks>.
@@ -1833,15 +1832,15 @@
12.2 Freedom for Web Pages
==========================
-If you use a site other than 'www.gnu.org', please make sure that the
+If you use a site other than âwww.gnu.orgâ, please make sure that the
site runs on free software alone. (It is ok if the site uses unreleased
-custom software, since that is free in a trivial sense: there's only one
+custom software, since that is free in a trivial sense: thereâs only one
user and it has the four freedoms.) If the web site for a GNU package
runs on non-free software, the public will see this, and it will have
the effect of granting legitimacy to the non-free program.
If you use multiple sites, they should all follow that criterion.
-Please don't link to a site that is about your package, which the public
+Please donât link to a site that is about your package, which the public
might perceive as connected with it and reflecting the position of its
developers, unless it follows that criterion.
@@ -1873,26 +1872,26 @@
include that too.
When there is only one manual, put it in a subdirectory called
-'manual'; the file 'manual/index.html' should have a link to the manual
+âmanualâ; the file âmanual/index.htmlâ should have a link to the manual
in each of its forms.
If the package has more than one manual, put each one in a
-subdirectory of 'manual', set up 'index.html' in each subdirectory to
-link to that manual in all its forms, and make 'manual/index.html' link
+subdirectory of âmanualâ, set up âindex.htmlâ in each subdirectory to
+link to that manual in all its forms, and make âmanual/index.htmlâ link
to each manual through its subdirectory.
See the section below for details on a script to make the job of
creating all these different formats and index pages easier.
We would like to list all GNU manuals on the page
-<https://www.gnu.org/manual>, so if yours isn't there, please send mail
-to 'address@hidden', asking them to add yours, and they will do so
-based on the contents of your 'manual' directory.
+<https://www.gnu.org/manual>, so if yours isnât there, please send mail
+to address@hidden, asking them to add yours, and they will do so
+based on the contents of your âmanualâ directory.
-12.3.1 Invoking 'gendocs.sh'
+12.3.1 Invoking âgendocs.shâ
----------------------------
-The script 'gendocs.sh' eases the task of generating the Texinfo
+The script âgendocs.shâ eases the task of generating the Texinfo
documentation output for your web pages section above. It has a
companion template file, used as the basis for the HTML index pages.
Both are available from the Gnulib development:
@@ -1911,32 +1910,32 @@
where YOURMANUAL is the short name for your package and YOURBUGLIST is
the email address for bug reports (which should be
-'address@hidden'). The script processes the file
-'YOURMANUAL.texinfo' (or '.texi' or '.txi'). For example:
address@hidden). The script processes the file
+âYOURMANUAL.texinfoâ (or â.texiâ or â.txiâ). For example:
cd .../texinfo/doc
# download gendocs.sh and gendocs_template
gendocs.sh --email address@hidden texinfo "GNU Texinfo manual"
- 'gendocs.sh' creates a subdirectory 'manual/' containing the manual
+ âgendocs.shâ creates a subdirectory âmanual/â containing the manual
generated in all the standard output formats: Info, HTML, DVI, and so
on, as well as the Texinfo source. You then need to move all those
files, retaining the subdirectories, into the web pages for your
package.
- You can specify the option '-o OUTDIR' to override the name 'manual'.
+ You can specify the option â-o OUTDIRâ to override the name
âmanualâ.
Any previous contents of OUTDIR will be deleted.
The second argument, with the description, is included as part of the
-HTML '<title>' of the overall 'manual/index.html' file. It should
+HTML â<title>â of the overall âmanual/index.htmlâ file. It should
include the name of the package being documented, as shown.
-'manual/index.html' is created by substitution from the file
-'gendocs_template'. (Feel free to modify the generic template for your
+âmanual/index.htmlâ is created by substitution from the file
+âgendocs_templateâ. (Feel free to modify the generic template for your
own purposes.)
- If you have several manuals, you'll need to run this script several
+ If you have several manuals, youâll need to run this script several
times with different arguments, specifying a different output directory
-with '-o' each time, and moving all the output to your web page. Then
+with â-oâ each time, and moving all the output to your web page. Then
write (by hand) an overall index.html with links to them all. For
example:
@@ -1945,37 +1944,34 @@
gendocs.sh --email address@hidden -o info info "GNU Info manual"
gendocs.sh --email address@hidden -o info-stnd info-stnd "GNU info-stnd
manual"
- By default, the script uses 'makeinfo' for generating HTML output.
-If you prefer to use 'texi2html', use the '--texi2html' command line
+ By default, the script uses âmakeinfoâ for generating HTML output.
+If you prefer to use âtexi2htmlâ, use the â--texi2htmlâ command line
option, e.g.:
gendocs --texi2html -o texinfo texinfo "GNU Texinfo manual"
The template files will automatically produce entries for additional
-HTML output generated by 'texi2html' (i.e., split by sections and
+HTML output generated by âtexi2htmlâ (i.e., split by sections and
chapters).
- You can set the environment variables 'MAKEINFO', 'TEXI2DVI', etc.,
-to control the programs that get executed, and 'GENDOCS_TEMPLATE_DIR' to
-control where the 'gendocs_template' file is found.
+ You can set the environment variables âMAKEINFOâ, âTEXI2DVIâ, etc.,
+to control the programs that get executed, and âGENDOCS_TEMPLATE_DIRâ to
+control where the âgendocs_templateâ file is found.
- As usual, run 'gendocs.sh --help' for a description of all the
+ As usual, run âgendocs.sh --helpâ for a description of all the
options, environment variables, and more information.
Please email bug reports, enhancement requests, or other
-correspondence about 'gendocs' to <address@hidden>.
+correspondence about âgendocsâ to <address@hidden>.
12.4 CVS Keywords in Web Pages
==============================
-Since 'www.gnu.org' works through CVS, CVS keywords in your manual, such
-as '$Log: maintain.txt,v $
-as 'Revision 1.111 2018/11/14 02:29:48 mikegerwitz
-as 'prep: Update maintainers
-as '
-as 'Note that this uses makeinfo 5.2, which is what was available on fencepost.
-as 'The previous version was generated with makeinfo 6.1.
-as '', need special treatment (even if you don't happen to maintain
+Since âwww.gnu.orgâ works through CVS, CVS keywords in your manual, such
+as â$Log: maintain.txt,v $
+as âRevision 1.112 2018/11/22 02:47:51 mikegerwitz
+as âprep/maintain: UTF-8 encoding
+as ââ, need special treatment (even if you donât happen to maintain
your manual in CVS).
If these keywords end up in the generated output as literal strings,
@@ -1989,29 +1985,29 @@
cvs add -ko FILE1 FILE2 ...
- See the "Keyword Substitution" section in the CVS manual, available
+ See the âKeyword Substitutionâ section in the CVS manual, available
from <https://cvs.nongnu.org>.
In Texinfo source, the recommended way to literally specify a
-"dollar" keyword is:
+âdollarâ keyword is:
@w{$}Log$
- The '@w' prevents keyword expansion in the Texinfo source itself.
-Also, 'makeinfo' notices the '@w' and generates output avoiding the
+ The address@hidden prevents keyword expansion in the Texinfo source itself.
+Also, âmakeinfoâ notices the address@hidden and generates output avoiding
the
literal keyword string.
13 Ethical and Philosophical Consideration
******************************************
The GNU project takes a strong stand for software freedom. Many times,
-this means you'll need to avoid certain technologies when their use
+this means youâll need to avoid certain technologies when their use
would conflict with our long-term goals.
Software patents threaten the advancement of free software and
freedom to program. There are so many software patents in the US that
any large program probably implements hundreds of patented techniques,
-unknown to the program's developers. It would be futile and
+unknown to the programâs developers. It would be futile and
self-defeating to try to find and avoid all these patents. But there
are some patents which we know are likely to be used to threaten free
software, so we make an effort to avoid the patented techniques. If you
@@ -2048,10 +2044,10 @@
Similarly, a GNU package should not require the use of non-free
software, including JavaScript, for the coordination of its development.
-For example, please don't use Transifex for translation of your software
+For example, please donât use Transifex for translation of your software
because it requires your translators to use non-free, JavaScript-based
editing tools. Instead, a service without any ethical concerns should
-be used, such as GNU's Pootle instance
+be used, such as GNUâs Pootle instance
(<https://chapters.gnu.org/pootle>) or The Translation Project
(<https://translationproject.org>).
@@ -2059,19 +2055,19 @@
for free software. The need for free documentation to come with free
software is now a major focus of the GNU project; to show that we are
serious about the need for free documentation, we must not contradict
-our position by recommending use of documentation that isn't free.
+our position by recommending use of documentation that isnât free.
- Please don't host discussions about your package in a service that
-requires nonfree software. For instance, Google+ "communities" require
-running a nonfree JavaScript program to post a message, so they can't be
+ Please donât host discussions about your package in a service that
+requires nonfree software. For instance, Google+ âcommunitiesâ require
+running a nonfree JavaScript program to post a message, so they canât be
used in the Free World. Google Groups has the same problem. To host
discussions there would be excluding people who live by free software
principles.
- Of course, you can't order people not to use such services to talk
+ Of course, you canât order people not to use such services to talk
with each other. What you can do is not legitimize them, and use your
influence to lead people away from them. For instance, where you say
-where to have discussions related to the program, don't list such a
+where to have discussions related to the program, donât list such a
place.
Finally, new issues concerning the ethics of software freedom come up
@@ -2085,13 +2081,12 @@
In GNU, we appreciate humor in our work.
GNU is a project of hackers, and hacking means playful cleverness.
-Even the name "GNU" is an example of playful cleverness--it is a
-recursive acronym for "GNU's Not Unix."
+Even the name âGNUâ is an example of playful clevernessâit is a
+recursive acronym for âGNUâs Not Unix.â
In that spirit, we prize occasional doses of humor in GNU packages.
Humor is not mandatory in a GNU package; we do not tell maintainers,
-"Make users smile, or else!" But when maintainers do that, we too
-smile.
+âMake users smile, or else!â But when maintainers do that, we too smile.
Nowadays, our humor-positive approach occasionally encounters direct,
blanket opposition. Some people advocate, and even demand, removal of
@@ -2105,8 +2100,8 @@
There are people who frown on anything that is slightly risqué or
controversial, including jokes. It would be a terrible shame for that
-attitude to prevail, so our policy is that the occasional risqué joke
-is ok. GNU is a 21st century project, not a 19th.
+attitude to prevail, so our policy is that the occasional risqué joke is
+ok. GNU is a 21st century project, not a 19th.
15 Other Politics
*****************
@@ -2135,7 +2130,7 @@
16.1 Free Software and Open Source
==================================
-The terms "free software" and "open source", while describing almost the
+The terms âfree softwareâ and âopen sourceâ, while describing almost
the
same category of software, stand for views based on fundamentally
different values. The free software movement is idealistic, and raises
issues of freedom, ethics, principle and what makes for a good society.
@@ -2144,15 +2139,15 @@
<https://www.gnu.org/philosophy/open-source-misses-the-point.html>.
The GNU Project is aligned with the free software movement. This
-doesn't mean that all GNU contributors and maintainers have to agree;
-your views on these issues are up to you, and you're entitled to express
+doesnât mean that all GNU contributors and maintainers have to agree;
+your views on these issues are up to you, and youâre entitled to express
them when speaking for yourself.
- However, due to the much greater publicity that the term "open
-source" receives, the GNU Project needs to overcome a widespread
-mistaken impression that GNU is _and always was_ an "open source"
-activity. For this reason, please use the term "free software", not
-"open source" or "FOSS", in GNU software releases, GNU documentation,
+ However, due to the much greater publicity that the term âopen
+sourceâ receives, the GNU Project needs to overcome a widespread
+mistaken impression that GNU is _and always was_ an âopen sourceâ
+activity. For this reason, please use the term âfree softwareâ, not
+âopen sourceâ or âFOSSâ, in GNU software releases, GNU documentation,
and announcements and articles that you publish in your role as the
maintainer of a GNU package. A reference to the URL given above, to
explain the difference, is a useful thing to include as well.
@@ -2163,12 +2158,12 @@
The GNU Project was formed to develop a free Unix-like operating system,
GNU. The existence of this system is our major accomplishment. However,
the widely used version of the GNU system, in which Linux is used as the
-kernel, is often called simply "Linux". As a result, most users don't
-know about the GNU Project's major accomplishment--or more precisely,
-they know about it, but don't realize it is the GNU Project's
+kernel, is often called simply âLinuxâ. As a result, most users donât
+know about the GNU Projectâs major accomplishmentâor more precisely,
+they know about it, but donât realize it is the GNU Projectâs
accomplishment and reason for existence. Even people who believe they
know the real history often believe that the goal of GNU was to develop
-"tools" or "utilities".
+âtoolsâ or âutilitiesâ.
To correct this confusion, we have made a years-long effort to
distinguish between Linux, the kernel that Linus Torvalds wrote, and
@@ -2184,22 +2179,22 @@
<https://www.gnu.org/gnu/linux-and-gnu.html>.
To make it clear that Linux is a kernel, not an operating system,
-please take care to avoid using the term "Linux system" in those
+please take care to avoid using the term âLinux systemâ in those
materials. If you want to have occasion to make a statement about
-systems in which the kernel is Linux, write "systems in which the kernel
-is Linux" or "systems with Linux as the kernel." That explicitly
+systems in which the kernel is Linux, write âsystems in which the kernel
+is Linuxâ or âsystems with Linux as the kernel.â That explicitly
contrasts the system and the kernel, and will help readers understand
the difference between the two. Please avoid simplified forms such as
-"Linux-based systems" because those fail to highlight the difference
+âLinux-based systemsâ because those fail to highlight the difference
between the kernel and the system, and could encourage readers to
overlook the distinction.
To contrast the GNU system proper with GNU/Linux, you can call it
-"GNU/Hurd" or "the GNU/Hurd system". However, when that contrast is not
-specifically the focus, please call it just "GNU" or "the GNU system".
+âGNU/Hurdâ or âthe GNU/Hurd systemâ. However, when that contrast is
not
+specifically the focus, please call it just âGNUâ or âthe GNU systemâ.
When referring to the collection of servers that is the higher level
-of the GNU kernel, please call it "the Hurd" or "the GNU Hurd". Note
+of the GNU kernel, please call it âthe Hurdâ or âthe GNU Hurdâ. Note
that this uses a space, not a slash.
For more about this point, see
@@ -2210,8 +2205,8 @@
Interviews and speeches about your package are an important channel for
informing the public about the GNU system and the ideas of the free
-software movement. Please avoid saying "open source" and avoid calling
-the GNU system "Linux", just as you would in the package itself (*note
+software movement. Please avoid saying âopen sourceâ and avoid calling
+the GNU system âLinuxâ, just as you would in the package itself (*note
Terminology::). Likewise, avoid promoting nonfree programs (*note
(standards)References::) as you would in the package itself.
@@ -2220,39 +2215,39 @@
to set them straight. Start the presentation with the answers to these
basic questions:
- * What GNU is (an operating system developed to be Unix-like and
+ ⢠What GNU is (an operating system developed to be Unix-like and
totally free software). It is good to mention
<https://www.gnu.org>.
- * What free software is (the users control it, so it doesn't control
+ ⢠What free software is (the users control it, so it doesnât control
them). It is good to state the four freedoms and/or refer to
<https://www.gnu.org/philosophy/free-sw.html>.
- * What GNU/Linux is (Linux filled the last gap in GNU). It is useful
+ ⢠What GNU/Linux is (Linux filled the last gap in GNU). It is useful
to refer to <https://www.gnu.org/gnu/linux-and-gnu.html>.
- * What the GNU Project is (the project to develop GNU).
+ ⢠What the GNU Project is (the project to develop GNU).
- * How your package fits in (it's part of GNU, and the work is part of
+ ⢠How your package fits in (itâs part of GNU, and the work is part of
the GNU Project).
If you feel a social pressure not to say these things, you may be
coming in contact with some who would prefer that these things not be
-said. That's precisely when we need your support most.
+said. Thatâs precisely when we need your support most.
- Please don't include advertisements or plugs for any company, product
+ Please donât include advertisements or plugs for any company, product
or service. Even if the product would meet the standards for the FSF to
endorse it, an ad for it is out of place in a presentation about a GNU
-package. Likewise, please don't include company slogans. Mention a
+package. Likewise, please donât include company slogans. Mention a
company only when called for by the subject matter.
A few GNU packages are actually business activities of a particular
company. In that case, it is ok to say so at the start. Otherwise,
please show that this is a project of the GNU Project, and avoid
-suggesting it is any company's project.
+suggesting it is any companyâs project.
If you are paid by a company to work on the GNU package, it is
-appropriate to thank the company in a discreet way, but please don't go
+appropriate to thank the company in a discreet way, but please donât go
beyond that.
Before you do a speech or interview, please contact the GNU Project
@@ -2269,17 +2264,17 @@
18 Hosting
**********
-We recommend using 'savannah.gnu.org' for the source code repository for
-your package, but that's not required. *Note Old Versions::, for more
+We recommend using âsavannah.gnu.orgâ for the source code repository for
+your package, but thatâs not required. *Note Old Versions::, for more
information about Savannah.
- We strongly urge you to use 'ftp.gnu.org' as the standard
+ We strongly urge you to use âftp.gnu.orgâ as the standard
distribution site for releases. Doing so makes it easier for developers
and users to find the latest GNU releases. However, it is ok to use
another server if you wish, provided it allows access from the general
public without limitation (for instance, without excluding any country).
- If you use a company's machine to hold the repository for your
+ If you use a companyâs machine to hold the repository for your
program, or as its release distribution site, please put this statement
in a prominent place on the site, so as to prevent people from getting
the wrong idea about the relationship between the package and the
@@ -2305,7 +2300,7 @@
As a maintainer, you might want to accept donations for your work,
especially if you pay for any of your own hosting/development
infrastructure. Following is some text you can adapt to your own
-situation, and use on your package's web site, 'README', or in wherever
+situation, and use on your packageâs web site, âREADMEâ, or in wherever
way you find it useful:
We appreciate contributions of any size -- donations enable us to spend
@@ -2330,9 +2325,9 @@
Thanks for your support!
- We don't recommend any specific payment service. However, GNU
+ We donât recommend any specific payment service. However, GNU
developers should not use a service that requires them to sign a
-proprietary software license, such as Google's payment service. Please
+proprietary software license, such as Googleâs payment service. Please
also avoid sites that requires users to run nonfree software in order to
donate. (This includes JavaScript software, so try it with LibreJS or
with JavaScript disabled.)
@@ -2382,37 +2377,37 @@
Here are a few methods that seem reasonable to use:
- * For something small, mail it to the list, and ask people to pick a
+ ⢠For something small, mail it to the list, and ask people to pick a
random number from 1 to 20, and read it if the number comes out as
10. This way, assuming 50% response, some 5 people will read the
piece.
- * For a larger work, divide your work into around 20 equal-sized
+ ⢠For a larger work, divide your work into around 20 equal-sized
parts, tell people where to get it, and ask each person to pick
randomly which part to read.
Be sure to specify the random choice procedure; otherwise people
will probably use a mental procedure that is not really random,
- such as "pick a part near the middle", and you will not get even
+ such as âpick a part near the middleâ, and you will not get even
coverage.
You can either divide up the work physically, into 20 separate
files, or describe a virtual division, such as by sections (if your
work has approximately 20 sections). If you do the latter, be sure
- to be precise about it--for example, do you want the material
- before the first section heading to count as a section, or not?
+ to be precise about itâfor example, do you want the material before
+ the first section heading to count as a section, or not?
- * For a job needing special skills, send an explanation of it, and
+ ⢠For a job needing special skills, send an explanation of it, and
ask people to send you mail if they volunteer for the job. When
you get enough volunteers, send another message to the list saying
- "I have enough volunteers, no more please."
+ âI have enough volunteers, no more please.â
Appendix A GNU Free Documentation License
*****************************************
Version 1.3, 3 November 2008
- Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
+ Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
<https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
@@ -2428,7 +2423,7 @@
author and publisher a way to get credit for their work, while not
being considered responsible for modifications made by others.
- This License is a kind of "copyleft", which means that derivative
+ This License is a kind of âcopyleftâ, which means that derivative
works of the document must themselves be free in the same sense.
It complements the GNU General Public License, which is a copyleft
license designed for free software.
@@ -2449,18 +2444,18 @@
be distributed under the terms of this License. Such a notice
grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The
- "Document", below, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You accept
+ âDocumentâ, below, refers to any such manual or work. Any member
+ of the public is a licensee, and is addressed as âyouâ. You accept
the license if you copy, modify or distribute the work in a way
requiring permission under copyright law.
- A "Modified Version" of the Document means any work containing the
+ A âModified Versionâ of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
- A "Secondary Section" is a named appendix or a front-matter section
+ A âSecondary Sectionâ is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall
+ publishers or authors of the Document to the Documentâs overall
subject (or to related matters) and contains nothing that could
fall directly within that overall subject. (Thus, if the Document
is in part a textbook of mathematics, a Secondary Section may not
@@ -2469,7 +2464,7 @@
of legal, commercial, philosophical, ethical or political position
regarding them.
- The "Invariant Sections" are certain Secondary Sections whose
+ The âInvariant Sectionsâ are certain Secondary Sections whose
titles are designated, as being those of Invariant Sections, in the
notice that says that the Document is released under this License.
If a section does not fit the above definition of Secondary then it
@@ -2477,13 +2472,13 @@
contain zero Invariant Sections. If the Document does not identify
any Invariant Sections then there are none.
- The "Cover Texts" are certain short passages of text that are
+ The âCover Textsâ are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
that says that the Document is released under this License. A
Front-Cover Text may be at most 5 words, and a Back-Cover Text may
be at most 25 words.
- A "Transparent" copy of the Document means a machine-readable copy,
+ A âTransparentâ copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed
@@ -2495,7 +2490,7 @@
been arranged to thwart or discourage subsequent modification by
readers is not Transparent. An image format is not Transparent if
used for any substantial amount of text. A copy that is not
- "Transparent" is called "Opaque".
+ âTransparentâ is called âOpaqueâ.
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
@@ -2508,23 +2503,23 @@
the machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
- The "Title Page" means, for a printed book, the title page itself,
+ The âTitle Pageâ means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
material this License requires to appear in the title page. For
- works in formats which do not have any title page as such, "Title
- Page" means the text near the most prominent appearance of the
- work's title, preceding the beginning of the body of the text.
+ works in formats which do not have any title page as such, âTitle
+ Pageâ means the text near the most prominent appearance of the
+ workâs title, preceding the beginning of the body of the text.
- The "publisher" means any person or entity that distributes copies
+ The âpublisherâ means any person or entity that distributes copies
of the Document to the public.
- A section "Entitled XYZ" means a named subunit of the Document
+ A section âEntitled XYZâ means a named subunit of the Document
whose title either is precisely XYZ or contains XYZ in parentheses
following text that translates XYZ in another language. (Here XYZ
stands for a specific section name mentioned below, such as
- "Acknowledgements", "Dedications", "Endorsements", or "History".)
- To "Preserve the Title" of such a section when you modify the
- Document means that it remains a section "Entitled XYZ" according
+ âAcknowledgementsâ, âDedicationsâ, âEndorsementsâ, or
âHistoryâ.)
+ To âPreserve the Titleâ of such a section when you modify the
+ Document means that it remains a section âEntitled XYZâ according
to this definition.
The Document may include Warranty Disclaimers next to the notice
@@ -2554,7 +2549,7 @@
If you publish printed copies (or copies in media that commonly
have printed covers) of the Document, numbering more than 100, and
- the Document's license notice requires Cover Texts, you must
+ the Documentâs license notice requires Cover Texts, you must
enclose the copies in covers that carry, clearly and legibly, all
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
@@ -2626,15 +2621,15 @@
the Addendum below.
G. Preserve in that license notice the full lists of Invariant
- Sections and required Cover Texts given in the Document's
+ Sections and required Cover Texts given in the Documentâs
license notice.
H. Include an unaltered copy of this License.
- I. Preserve the section Entitled "History", Preserve its Title,
+ I. Preserve the section Entitled âHistoryâ, Preserve its Title,
and add to it an item stating at least the title, year, new
authors, and publisher of the Modified Version as given on the
- Title Page. If there is no section Entitled "History" in the
+ Title Page. If there is no section Entitled âHistoryâ in the
Document, create one stating the title, year, authors, and
publisher of the Document as given on its Title Page, then add
an item describing the Modified Version as stated in the
@@ -2644,12 +2639,12 @@
for public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
previous versions it was based on. These may be placed in the
- "History" section. You may omit a network location for a work
+ âHistoryâ section. You may omit a network location for a work
that was published at least four years before the Document
itself, or if the original publisher of the version it refers
to gives permission.
- K. For any section Entitled "Acknowledgements" or "Dedications",
+ K. For any section Entitled âAcknowledgementsâ or âDedicationsâ,
Preserve the Title of the section, and preserve in the section
all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.
@@ -2658,11 +2653,11 @@
in their text and in their titles. Section numbers or the
equivalent are not considered part of the section titles.
- M. Delete any section Entitled "Endorsements". Such a section
+ M. Delete any section Entitled âEndorsementsâ. Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled
- "Endorsements" or to conflict in title with any Invariant
+ âEndorsementsâ or to conflict in title with any Invariant
Section.
O. Preserve any Warranty Disclaimers.
@@ -2671,15 +2666,15 @@
appendices that qualify as Secondary Sections and contain no
material copied from the Document, you may at your option designate
some or all of these sections as invariant. To do this, add their
- titles to the list of Invariant Sections in the Modified Version's
+ titles to the list of Invariant Sections in the Modified Versionâs
license notice. These titles must be distinct from any other
section titles.
- You may add a section Entitled "Endorsements", provided it contains
+ You may add a section Entitled âEndorsementsâ, provided it contains
nothing but endorsements of your Modified Version by various
- parties--for example, statements of peer review or that the text
- has been approved by an organization as the authoritative
- definition of a standard.
+ partiesâfor example, statements of peer review or that the text has
+ been approved by an organization as the authoritative definition of
+ a standard.
You may add a passage of up to five words as a Front-Cover Text,
and a passage of up to 25 words as a Back-Cover Text, to the end of
@@ -2717,10 +2712,10 @@
combined work.
In the combination, you must combine any sections Entitled
- "History" in the various original documents, forming one section
- Entitled "History"; likewise combine any sections Entitled
- "Acknowledgements", and any sections Entitled "Dedications". You
- must delete all sections Entitled "Endorsements."
+ âHistoryâ in the various original documents, forming one section
+ Entitled âHistoryâ; likewise combine any sections Entitled
+ âAcknowledgementsâ, and any sections Entitled âDedicationsâ. You
+ must delete all sections Entitled âEndorsements.â
6. COLLECTIONS OF DOCUMENTS
@@ -2741,16 +2736,16 @@
A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
- storage or distribution medium, is called an "aggregate" if the
+ storage or distribution medium, is called an âaggregateâ if the
copyright resulting from the compilation is not used to limit the
- legal rights of the compilation's users beyond what the individual
+ legal rights of the compilationâs users beyond what the individual
works permit. When the Document is included in an aggregate, this
License does not apply to the other works in the aggregate which
are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half
- of the entire aggregate, the Document's Cover Texts may be placed
+ of the entire aggregate, the Documentâs Cover Texts may be placed
on covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic
form. Otherwise they must appear on printed covers that bracket
@@ -2772,8 +2767,8 @@
this License or a notice or disclaimer, the original version will
prevail.
- If a section in the Document is Entitled "Acknowledgements",
- "Dedications", or "History", the requirement (section 4) to
+ If a section in the Document is Entitled âAcknowledgementsâ,
+ âDedicationsâ, or âHistoryâ, the requirement (section 4) to
Preserve its Title (section 1) will typically require changing the
actual title.
@@ -2814,7 +2809,7 @@
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
- version of this License "or any later version" applies to it, you
+ version of this License âor any later versionâ applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
published (not as a draft) by the Free Software Foundation. If the
@@ -2822,29 +2817,29 @@
choose any version ever published (not as a draft) by the Free
Software Foundation. If the Document specifies that a proxy can
decide which future versions of this License can be used, that
- proxy's public statement of acceptance of a version permanently
+ proxyâs public statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
11. RELICENSING
- "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
+ âMassive Multiauthor Collaboration Siteâ (or âMMC Siteâ) means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server.
- A "Massive Multiauthor Collaboration" (or "MMC") contained in the
+ A âMassive Multiauthor Collaborationâ (or âMMCâ) contained in the
site means any set of copyrightable works thus published on the MMC
site.
- "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
+ âCC-BY-SAâ means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
- "Incorporate" means to publish or republish a Document, in whole or
+ âIncorporateâ means to publish or republish a Document, in whole or
in part, as part of another Document.
- An MMC is "eligible for relicensing" if it is licensed under this
+ An MMC is âeligible for relicensingâ if it is licensed under this
License, and if all works that were first published under this
License somewhere other than this MMC, and subsequently
incorporated in whole or in part into the MMC, (1) had no cover
@@ -2871,7 +2866,7 @@
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the âwithâ¦Texts.â line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -2892,28 +2887,28 @@
* Menu:
* $ keywords in web pages: CVS Keywords in Web Pages.
- (line 1970)
-* '/gd/gnuorg' directory: Copyright Papers. (line 281)
+ (line 1969)
+* â/gd/gnuorgâ directory: Copyright Papers. (line 281)
* advisory committee: Getting Help. (line 133)
-* 'alpha.gnu.org', test release site: Test Releases. (line 1306)
+* âalpha.gnu.orgâ, test release site: Test Releases. (line 1305)
* announcement mailing list, project-specific: Announcements.
- (line 1737)
-* announcements: Announcements. (line 1721)
+ (line 1736)
+* announcements: Announcements. (line 1720)
* announcements, mailing list for: Standard Mailing Lists.
(line 1069)
* assignments, copyright: Copyright Papers. (line 247)
-* 'AUTHORS' file: Recording Contributors.
+* âAUTHORSâ file: Recording Contributors.
(line 507)
* automake: Distribution tar Files.
- (line 1229)
-* beta releases: Test Releases. (line 1306)
-* bug reports, email tracker for: Replying to Mail. (line 1152)
+ (line 1228)
+* beta releases: Test Releases. (line 1305)
+* bug reports, email tracker for: Replying to Mail. (line 1151)
* bug reports, handling: Replying to Mail. (line 1116)
-* bug reports, web tracker for: Replying to Mail. (line 1152)
+* bug reports, web tracker for: Replying to Mail. (line 1151)
* <address@hidden>: Standard Mailing Lists.
(line 1055)
-* 'address@hidden' email address: Preface. (line 99)
-* contents of announcements: Announcements. (line 1743)
+* address@hidden email address: Preface. (line 99)
+* contents of announcements: Announcements. (line 1742)
* contributions, accepting: Clean Ups. (line 962)
* copyright notices in program files: Copyright Notices. (line 583)
* copyright papers: Copyright Papers. (line 247)
@@ -2921,78 +2916,78 @@
(line 1082)
* crediting authors: Crediting Authors. (line 950)
* CVS keywords in web pages: CVS Keywords in Web Pages.
- (line 1970)
-* CVS repository: Hosting. (line 2265)
+ (line 1969)
+* CVS repository: Hosting. (line 2263)
* data base of GNU copyright assignments: Copyright Papers. (line 275)
* development method, open source: Free Software and Open Source.
- (line 2131)
+ (line 2129)
* development resources: GNU Accounts and Resources.
(line 154)
* diff: Distribution Patches.
- (line 1253)
+ (line 1252)
* directive file, for FTP uploads: FTP Upload Directive File.
- (line 1489)
+ (line 1488)
* directives for ftp uploads, standalone: FTP Upload Standalone Directives.
- (line 1613)
+ (line 1612)
* directory trees, in ftp uploads: FTP Upload Directory Trees.
- (line 1560)
+ (line 1559)
* Directory, Free Software: Free Software Directory.
- (line 2350)
+ (line 2348)
* disclaimers: Copyright Papers. (line 247)
* distribution, tar files: Distribution tar Files.
- (line 1203)
+ (line 1202)
* documentation output, generating: Invoking gendocs.sh.
- (line 1894)
-* Donations, for packages: Donations. (line 2298)
+ (line 1893)
+* Donations, for packages: Donations. (line 2296)
* down, when GNU machines are: Getting Help. (line 140)
* email: Mail. (line 1041)
* ethics: Ethical and Philosophical
Consideration.
- (line 2000)
+ (line 1999)
* FDL, GNU Free Documentation License: GNU Free Documentation License.
- (line 2406)
-* 'fencepost.gnu.org' GNU login host: GNU Accounts and Resources.
+ (line 2404)
+* âfencepost.gnu.orgâ GNU login host: GNU Accounts and Resources.
(line 154)
* formats for documentation, desired: Manuals on Web Pages.
- (line 1868)
+ (line 1867)
* Free Software Directory: Free Software Directory.
- (line 2350)
+ (line 2348)
* free software movement: Free Software and Open Source.
- (line 2131)
+ (line 2129)
* FSF system administrators: Getting Help. (line 146)
-* FTP site: Hosting. (line 2265)
+* FTP site: Hosting. (line 2263)
* ftp uploads, automated: Automated FTP Uploads.
- (line 1356)
+ (line 1355)
* FTP uploads, of release files: FTP Upload Release File Triplet.
- (line 1466)
-* 'ftp.gnu.org', the GNU release site: Distribution on ftp.gnu.org.
- (line 1295)
+ (line 1465)
+* âftp.gnu.orgâ, the GNU release site: Distribution on ftp.gnu.org.
+ (line 1294)
* gendocs.sh: Invoking gendocs.sh.
- (line 1894)
+ (line 1893)
* generating documentation output: Invoking gendocs.sh.
- (line 1894)
+ (line 1893)
* GNU ftp site: Distribution on ftp.gnu.org.
- (line 1295)
+ (line 1294)
* GNU system administrators: Getting Help. (line 146)
-* GNU/Linux: GNU and Linux. (line 2156)
-* 'gnustandards' project repository: Preface. (line 99)
-* 'address@hidden' mailing list: Preface. (line 107)
+* GNU/Linux: GNU and Linux. (line 2154)
+* âgnustandardsâ project repository: Preface. (line 99)
+* address@hidden mailing list: Preface. (line 107)
* help for users, mailing list for: Standard Mailing Lists.
(line 1063)
* help requests, handling: Replying to Mail. (line 1116)
* help, getting: Getting Help. (line 127)
* hierarchy, under ftp upload directory: FTP Upload Directory Trees.
- (line 1560)
-* hosting: Hosting. (line 2265)
-* <https://bugs.gnu.org>: Replying to Mail. (line 1152)
-* <https://planet.gnu.org>: Announcements. (line 1729)
+ (line 1559)
+* hosting: Hosting. (line 2263)
+* <https://bugs.gnu.org>: Replying to Mail. (line 1151)
+* <https://planet.gnu.org>: Announcements. (line 1728)
* <https://quitter.im/fsfstatus>: Getting Help. (line 140)
* Hydra: GNU Accounts and Resources.
(line 177)
-* 'info-gnu' mailing list: Announcements. (line 1721)
+* âinfo-gnuâ mailing list: Announcements. (line 1720)
* legal matters: Legal Matters. (line 241)
* legal papers for changes in manuals: Copyright Papers. (line 367)
* license notices in program files: License Notices. (line 683)
-* Linux: GNU and Linux. (line 2156)
+* Linux: GNU and Linux. (line 2154)
* mailing list for bug reports: Standard Mailing Lists.
(line 1048)
* mailing lists, creating: Creating Mailing Lists.
@@ -3000,76 +2995,76 @@
* mailing lists, standard names of: Standard Mailing Lists.
(line 1048)
* <address@hidden>: Stepping Down. (line 192)
-* 'address@hidden' mailing list: Getting Help. (line 127)
-* Money, donated to packages: Donations. (line 2298)
+* address@hidden mailing list: Getting Help. (line 127)
+* Money, donated to packages: Donations. (line 2296)
* movement, free software: Free Software and Open Source.
- (line 2131)
+ (line 2129)
* open source: Free Software and Open Source.
- (line 2131)
+ (line 2129)
* outage, of GNU machines: Getting Help. (line 140)
* patch: Distribution Patches.
- (line 1253)
+ (line 1252)
* patches, against previous releases: Distribution Patches.
- (line 1235)
+ (line 1234)
* philosophy: Ethical and Philosophical
Consideration.
- (line 2000)
+ (line 1999)
* Piercy, Marge: Preface. (line 113)
-* 'platform-testers' mailing list: GNU Accounts and Resources.
+* âplatform-testersâ mailing list: GNU Accounts and Resources.
(line 177)
-* pretest releases: Test Releases. (line 1306)
+* pretest releases: Test Releases. (line 1305)
* proofreading: Using the Proofreaders List.
- (line 2361)
+ (line 2359)
* quality of changes suggested by others: Clean Ups. (line 962)
* RCS keywords in web pages: CVS Keywords in Web Pages.
- (line 1970)
+ (line 1969)
* recording contributors: Recording Contributors.
(line 476)
* registration for uploads: Automated Upload Registration.
- (line 1367)
-* release site: Hosting. (line 2265)
+ (line 1366)
+* release site: Hosting. (line 2263)
* replacing uploaded files: FTP Upload File Replacement.
- (line 1581)
-* repository: Hosting. (line 2265)
+ (line 1580)
+* repository: Hosting. (line 2263)
* resigning as maintainer: Stepping Down. (line 183)
* resources for GNU developers: GNU Accounts and Resources.
(line 154)
* responding to bug reports: Replying to Mail. (line 1116)
-* Savannah repository for 'gnustandards': Preface. (line 99)
-* Savannah, news area: Announcements. (line 1729)
-* 'address@hidden' mailing list: Old Versions. (line 1188)
-* 'address@hidden': Old Versions. (line 1175)
+* Savannah repository for âgnustandardsâ: Preface. (line 99)
+* Savannah, news area: Announcements. (line 1728)
+* address@hidden mailing list: Old Versions. (line 1187)
+* address@hidden: Old Versions. (line 1174)
* shell account, on fencepost: GNU Accounts and Resources.
(line 154)
-* source repository: Hosting. (line 2265)
+* source repository: Hosting. (line 2263)
* spam prevention: Creating Mailing Lists.
(line 1099)
* standalone directives, for ftp uploads: FTP Upload Standalone Directives.
- (line 1613)
+ (line 1612)
* standard mailing lists: Standard Mailing Lists.
(line 1048)
* stepping down as maintainer: Stepping Down. (line 183)
* sysadmin, FSF: Getting Help. (line 146)
-* terminology: Terminology. (line 2124)
-* test releases: Test Releases. (line 1306)
+* terminology: Terminology. (line 2122)
+* test releases: Test Releases. (line 1305)
* time stamp in diffs: Distribution Patches.
- (line 1253)
+ (line 1252)
* uploads: Automated Upload Procedure.
- (line 1419)
+ (line 1418)
* uploads, directory trees in: FTP Upload Directory Trees.
- (line 1560)
+ (line 1559)
* uploads, registration for: Automated Upload Registration.
- (line 1367)
+ (line 1366)
* uploads, replacing: FTP Upload File Replacement.
- (line 1581)
-* version control: Old Versions. (line 1163)
-* version control system: Hosting. (line 2265)
-* web pages: Web Pages. (line 1766)
+ (line 1580)
+* version control: Old Versions. (line 1162)
+* version control system: Hosting. (line 2263)
+* web pages: Web Pages. (line 1765)
* web pages, and CVS keywords: CVS Keywords in Web Pages.
- (line 1970)
+ (line 1969)
* web pages, freedom for: Freedom for Web Pages.
- (line 1835)
+ (line 1834)
* web pages, hosting for: Hosting for Web Pages.
- (line 1810)
+ (line 1809)
* web pages, including manuals on: Manuals on Web Pages.
- (line 1868)
+ (line 1867)
Index: maintain.txt.gz
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.txt.gz,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -b -r1.108 -r1.109
Binary files /var/tmp/cvsGRokkd and /var/tmp/cvs7I0ibI differ
Index: html_node/Announcements.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Announcements.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Announcements.html 14 Nov 2018 02:29:48 -0000 1.105
+++ html_node/Announcements.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Automated-FTP-Uploads.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Automated-FTP-Uploads.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Automated-FTP-Uploads.html 14 Nov 2018 02:29:48 -0000
1.105
+++ html_node/Automated-FTP-Uploads.html 22 Nov 2018 02:47:52 -0000
1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Automated-Upload-Procedure.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Automated-Upload-Procedure.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Automated-Upload-Procedure.html 14 Nov 2018 02:29:48 -0000
1.105
+++ html_node/Automated-Upload-Procedure.html 22 Nov 2018 02:47:52 -0000
1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Automated-Upload-Registration.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/Automated-Upload-Registration.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Automated-Upload-Registration.html 14 Nov 2018 02:29:48
-0000 1.105
+++ html_node/Automated-Upload-Registration.html 22 Nov 2018 02:47:52
-0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Binary-Distribution.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Binary-Distribution.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- html_node/Binary-Distribution.html 14 Nov 2018 02:29:48 -0000 1.14
+++ html_node/Binary-Distribution.html 22 Nov 2018 02:47:52 -0000 1.15
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/CVS-Keywords-in-Web-Pages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/CVS-Keywords-in-Web-Pages.html,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -b -r1.104 -r1.105
--- html_node/CVS-Keywords-in-Web-Pages.html 14 Nov 2018 02:29:48 -0000
1.104
+++ html_node/CVS-Keywords-in-Web-Pages.html 22 Nov 2018 02:47:52 -0000
1.105
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Canonical-License-Sources.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Canonical-License-Sources.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -b -r1.89 -r1.90
--- html_node/Canonical-License-Sources.html 14 Nov 2018 02:29:48 -0000
1.89
+++ html_node/Canonical-License-Sources.html 22 Nov 2018 02:47:52 -0000
1.90
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Clean-Ups.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Clean-Ups.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Clean-Ups.html 14 Nov 2018 02:29:48 -0000 1.105
+++ html_node/Clean-Ups.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Copying-from-Other-Packages.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/Copying-from-Other-Packages.html,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -b -r1.93 -r1.94
--- html_node/Copying-from-Other-Packages.html 14 Nov 2018 02:29:49 -0000
1.93
+++ html_node/Copying-from-Other-Packages.html 22 Nov 2018 02:47:52 -0000
1.94
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Copyright-Notices.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Copyright-Notices.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Copyright-Notices.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Copyright-Notices.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Copyright-Papers.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Copyright-Papers.html,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -b -r1.107 -r1.108
--- html_node/Copyright-Papers.html 14 Nov 2018 02:29:49 -0000 1.107
+++ html_node/Copyright-Papers.html 22 Nov 2018 02:47:52 -0000 1.108
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Creating-Mailing-Lists.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Creating-Mailing-Lists.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- html_node/Creating-Mailing-Lists.html 14 Nov 2018 02:29:49 -0000
1.56
+++ html_node/Creating-Mailing-Lists.html 22 Nov 2018 02:47:52 -0000
1.57
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Crediting-Authors.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Crediting-Authors.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- html_node/Crediting-Authors.html 14 Nov 2018 02:29:49 -0000 1.14
+++ html_node/Crediting-Authors.html 22 Nov 2018 02:47:52 -0000 1.15
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Distribution-Patches.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Distribution-Patches.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Distribution-Patches.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Distribution-Patches.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Distribution-on-ftp_002egnu_002eorg.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/Distribution-on-ftp_002egnu_002eorg.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Distribution-on-ftp_002egnu_002eorg.html 14 Nov 2018 02:29:49
-0000 1.105
+++ html_node/Distribution-on-ftp_002egnu_002eorg.html 22 Nov 2018 02:47:52
-0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Distribution-tar-Files.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Distribution-tar-Files.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Distribution-tar-Files.html 14 Nov 2018 02:29:49 -0000
1.105
+++ html_node/Distribution-tar-Files.html 22 Nov 2018 02:47:52 -0000
1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Distributions.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Distributions.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Distributions.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Distributions.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Donations.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Donations.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -b -r1.48 -r1.49
--- html_node/Donations.html 14 Nov 2018 02:29:49 -0000 1.48
+++ html_node/Donations.html 22 Nov 2018 02:47:52 -0000 1.49
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Ethical-and-Philosophical-Consideration.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/Ethical-and-Philosophical-Consideration.html,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -b -r1.106 -r1.107
--- html_node/Ethical-and-Philosophical-Consideration.html 14 Nov 2018
02:29:49 -0000 1.106
+++ html_node/Ethical-and-Philosophical-Consideration.html 22 Nov 2018
02:47:52 -0000 1.107
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/External-Libraries.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/External-Libraries.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/External-Libraries.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/External-Libraries.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/FSF_002dCopyrighted-Package.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/FSF_002dCopyrighted-Package.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- html_node/FSF_002dCopyrighted-Package.html 14 Nov 2018 02:29:49 -0000
1.31
+++ html_node/FSF_002dCopyrighted-Package.html 22 Nov 2018 02:47:52 -0000
1.32
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -b -r1.95 -r1.96
--- html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html 14 Nov 2018
02:29:49 -0000 1.95
+++ html_node/FTP-Upload-Directive-File-_002d-v1_002e0.html 22 Nov 2018
02:47:52 -0000 1.96
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -b -r1.95 -r1.96
--- html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html 14 Nov 2018
02:29:49 -0000 1.95
+++ html_node/FTP-Upload-Directive-File-_002d-v1_002e1.html 22 Nov 2018
02:47:52 -0000 1.96
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/FTP-Upload-Directive-File.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/FTP-Upload-Directive-File.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- html_node/FTP-Upload-Directive-File.html 14 Nov 2018 02:29:49 -0000
1.23
+++ html_node/FTP-Upload-Directive-File.html 22 Nov 2018 02:47:52 -0000
1.24
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/FTP-Upload-Directory-Trees.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/FTP-Upload-Directory-Trees.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- html_node/FTP-Upload-Directory-Trees.html 14 Nov 2018 02:29:49 -0000
1.23
+++ html_node/FTP-Upload-Directory-Trees.html 22 Nov 2018 02:47:52 -0000
1.24
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/FTP-Upload-File-Replacement.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/FTP-Upload-File-Replacement.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- html_node/FTP-Upload-File-Replacement.html 14 Nov 2018 02:29:49 -0000
1.23
+++ html_node/FTP-Upload-File-Replacement.html 22 Nov 2018 02:47:52 -0000
1.24
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/FTP-Upload-Release-File-Triplet.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/FTP-Upload-Release-File-Triplet.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- html_node/FTP-Upload-Release-File-Triplet.html 14 Nov 2018 02:29:49
-0000 1.23
+++ html_node/FTP-Upload-Release-File-Triplet.html 22 Nov 2018 02:47:52
-0000 1.24
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/FTP-Upload-Standalone-Directives.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/FTP-Upload-Standalone-Directives.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- html_node/FTP-Upload-Standalone-Directives.html 14 Nov 2018 02:29:49
-0000 1.23
+++ html_node/FTP-Upload-Standalone-Directives.html 22 Nov 2018 02:47:52
-0000 1.24
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Free-Software-Directory.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Free-Software-Directory.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Free-Software-Directory.html 14 Nov 2018 02:29:49 -0000
1.105
+++ html_node/Free-Software-Directory.html 22 Nov 2018 02:47:52 -0000
1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Free-Software-and-Open-Source.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/Free-Software-and-Open-Source.html,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -b -r1.107 -r1.108
--- html_node/Free-Software-and-Open-Source.html 14 Nov 2018 02:29:49
-0000 1.107
+++ html_node/Free-Software-and-Open-Source.html 22 Nov 2018 02:47:52
-0000 1.108
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Freedom-for-Web-Pages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Freedom-for-Web-Pages.html,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -b -r1.64 -r1.65
--- html_node/Freedom-for-Web-Pages.html 14 Nov 2018 02:29:49 -0000
1.64
+++ html_node/Freedom-for-Web-Pages.html 22 Nov 2018 02:47:52 -0000
1.65
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/GNU-Accounts-and-Resources.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/GNU-Accounts-and-Resources.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- html_node/GNU-Accounts-and-Resources.html 14 Nov 2018 02:29:49 -0000
1.35
+++ html_node/GNU-Accounts-and-Resources.html 22 Nov 2018 02:47:52 -0000
1.36
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/GNU-Free-Documentation-License.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/GNU-Free-Documentation-License.html,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -b -r1.82 -r1.83
--- html_node/GNU-Free-Documentation-License.html 14 Nov 2018 02:29:49
-0000 1.82
+++ html_node/GNU-Free-Documentation-License.html 22 Nov 2018 02:47:52
-0000 1.83
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/GNU-and-Linux.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/GNU-and-Linux.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/GNU-and-Linux.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/GNU-and-Linux.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Getting-Help.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Getting-Help.html,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -b -r1.59 -r1.60
--- html_node/Getting-Help.html 14 Nov 2018 02:29:49 -0000 1.59
+++ html_node/Getting-Help.html 22 Nov 2018 02:47:52 -0000 1.60
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Hosting-for-Web-Pages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Hosting-for-Web-Pages.html,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -b -r1.64 -r1.65
--- html_node/Hosting-for-Web-Pages.html 14 Nov 2018 02:29:49 -0000
1.64
+++ html_node/Hosting-for-Web-Pages.html 22 Nov 2018 02:47:52 -0000
1.65
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Hosting.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Hosting.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Hosting.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Hosting.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Humor.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Humor.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- html_node/Humor.html 14 Nov 2018 02:37:09 -0000 1.1
+++ html_node/Humor.html 22 Nov 2018 02:47:52 -0000 1.2
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
@@ -96,9 +96,9 @@
humorous, so we do not defend every joke obtusely to the bitter end.
But <em>the fact that it is a joke</em> is not a valid objection.
</p>
-<p>There are people who frown on anything that is slightly risqué or
+<p>There are people who frown on anything that is slightly risqué or
controversial, including jokes. It would be a terrible shame for that
-attitude to prevail, so our policy is that the occasional risqué joke
+attitude to prevail, so our policy is that the occasional risqué joke
is ok. GNU is a 21st century project, not a 19th.
</p>
Index: html_node/Index.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Index.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Index.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Index.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Interviews-and-Speeches.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Interviews-and-Speeches.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- html_node/Interviews-and-Speeches.html 14 Nov 2018 02:29:49 -0000
1.30
+++ html_node/Interviews-and-Speeches.html 22 Nov 2018 02:47:52 -0000
1.31
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Invoking-gendocs_002esh.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Invoking-gendocs_002esh.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Invoking-gendocs_002esh.html 14 Nov 2018 02:29:49 -0000
1.105
+++ html_node/Invoking-gendocs_002esh.html 22 Nov 2018 02:47:52 -0000
1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Legal-Matters.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Legal-Matters.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Legal-Matters.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Legal-Matters.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Legally-Significant.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Legally-Significant.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Legally-Significant.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Legally-Significant.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/License-Notices-for-Code.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/License-Notices-for-Code.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -b -r1.89 -r1.90
--- html_node/License-Notices-for-Code.html 14 Nov 2018 02:29:49 -0000
1.89
+++ html_node/License-Notices-for-Code.html 22 Nov 2018 02:47:52 -0000
1.90
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/License-Notices-for-Documentation.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/License-Notices-for-Documentation.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -b -r1.89 -r1.90
--- html_node/License-Notices-for-Documentation.html 14 Nov 2018 02:29:49
-0000 1.89
+++ html_node/License-Notices-for-Documentation.html 22 Nov 2018 02:47:52
-0000 1.90
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/License-Notices-for-Other-Files.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/License-Notices-for-Other-Files.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -b -r1.89 -r1.90
--- html_node/License-Notices-for-Other-Files.html 14 Nov 2018 02:29:49
-0000 1.89
+++ html_node/License-Notices-for-Other-Files.html 22 Nov 2018 02:47:52
-0000 1.90
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/License-Notices.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/License-Notices.html,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -b -r1.107 -r1.108
--- html_node/License-Notices.html 14 Nov 2018 02:29:49 -0000 1.107
+++ html_node/License-Notices.html 22 Nov 2018 02:47:52 -0000 1.108
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Licensing-of-GNU-Packages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Licensing-of-GNU-Packages.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -b -r1.45 -r1.46
--- html_node/Licensing-of-GNU-Packages.html 14 Nov 2018 02:29:49 -0000
1.45
+++ html_node/Licensing-of-GNU-Packages.html 22 Nov 2018 02:47:52 -0000
1.46
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Mail.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Mail.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Mail.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Mail.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Manuals-on-Web-Pages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Manuals-on-Web-Pages.html,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -b -r1.64 -r1.65
--- html_node/Manuals-on-Web-Pages.html 14 Nov 2018 02:29:49 -0000 1.64
+++ html_node/Manuals-on-Web-Pages.html 22 Nov 2018 02:47:52 -0000 1.65
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Non_002dFSF_002dCopyrighted-Package.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/Non_002dFSF_002dCopyrighted-Package.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- html_node/Non_002dFSF_002dCopyrighted-Package.html 14 Nov 2018 02:29:49
-0000 1.31
+++ html_node/Non_002dFSF_002dCopyrighted-Package.html 22 Nov 2018 02:47:52
-0000 1.32
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Old-Versions.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Old-Versions.html,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -b -r1.107 -r1.108
--- html_node/Old-Versions.html 14 Nov 2018 02:29:49 -0000 1.107
+++ html_node/Old-Versions.html 22 Nov 2018 02:47:52 -0000 1.108
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Other-Politics.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Other-Politics.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- html_node/Other-Politics.html 14 Nov 2018 02:37:09 -0000 1.1
+++ html_node/Other-Politics.html 22 Nov 2018 02:47:52 -0000 1.2
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Platforms.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Platforms.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Platforms.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Platforms.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Preface.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Preface.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Preface.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Preface.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
@@ -114,7 +114,7 @@
work, and to enable per to feel person has done the right thing.”
</p>
<p>This release of the GNU Maintainer Information was last updated
-October 24, 2018.
+November 21, 2018.
</p>
<hr>
Index: html_node/Recording-Contributors.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Recording-Contributors.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Recording-Contributors.html 14 Nov 2018 02:29:49 -0000
1.105
+++ html_node/Recording-Contributors.html 22 Nov 2018 02:47:52 -0000
1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Recruiting-Developers.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Recruiting-Developers.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Recruiting-Developers.html 14 Nov 2018 02:29:49 -0000
1.105
+++ html_node/Recruiting-Developers.html 22 Nov 2018 02:47:52 -0000
1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Replying-to-Mail.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Replying-to-Mail.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- html_node/Replying-to-Mail.html 14 Nov 2018 02:29:49 -0000 1.56
+++ html_node/Replying-to-Mail.html 22 Nov 2018 02:47:52 -0000 1.57
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Standard-Mailing-Lists.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Standard-Mailing-Lists.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- html_node/Standard-Mailing-Lists.html 14 Nov 2018 02:29:49 -0000
1.56
+++ html_node/Standard-Mailing-Lists.html 22 Nov 2018 02:47:52 -0000
1.57
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Stepping-Down.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Stepping-Down.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Stepping-Down.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Stepping-Down.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Terminology.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Terminology.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Terminology.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Terminology.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Test-Releases.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Test-Releases.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Test-Releases.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Test-Releases.html 22 Nov 2018 02:47:52 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Using-the-Proofreaders-List.html
===================================================================
RCS file:
/web/www/www/prep/maintain/html_node/Using-the-Proofreaders-List.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Using-the-Proofreaders-List.html 14 Nov 2018 02:29:49 -0000
1.105
+++ html_node/Using-the-Proofreaders-List.html 22 Nov 2018 02:47:53 -0000
1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/Web-Pages.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/Web-Pages.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/Web-Pages.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/Web-Pages.html 22 Nov 2018 02:47:53 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
Index: html_node/index.html
===================================================================
RCS file: /web/www/www/prep/maintain/html_node/index.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -b -r1.105 -r1.106
--- html_node/index.html 14 Nov 2018 02:29:49 -0000 1.105
+++ html_node/index.html 22 Nov 2018 02:47:53 -0000 1.106
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- Information for maintainers of GNU software, last updated October 24,
2018.
+<!-- Information for maintainers of GNU software, last updated November 21,
2018.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
@@ -170,7 +170,7 @@
<a name="Version"></a>
<h1 class="top">Version</h1>
-<p>Information for maintainers of GNU software, last updated October 24, 2018.
+<p>Information for maintainers of GNU software, last updated November 21, 2018.
</p>
<p>Copyright © 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,