[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] * doc/gnulib-readme.texi: Minor fixups.

From: Paul Eggert
Subject: [PATCH] * doc/gnulib-readme.texi: Minor fixups.
Date: Thu, 27 Dec 2012 17:41:13 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0

I pushed these minor fixes.

 ChangeLog              |  5 +++++
 doc/gnulib-readme.texi | 49 ++++++++++++-------------------------------------
 2 files changed, 17 insertions(+), 37 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 0908d93..b3fdd2b 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2012-12-27  Paul Eggert  <address@hidden>
+ * doc/gnulib-readme.texi: Minor fixups.
+       (Portability guidelines): Modernize URLs.  Remove some repetition.
+       (Indent with spaces not TABs): Reword to avoid too-long lines.
+       Remove some '@ifset standalone' stuff that isn't used.
        * doc/gnulib-readme.texi (Portability guidelines):
        ctype.h, not ctime.h.
diff --git a/doc/gnulib-readme.texi b/doc/gnulib-readme.texi
index 1ce104c..b389e41 100644
--- a/doc/gnulib-readme.texi
+++ b/doc/gnulib-readme.texi
@@ -46,8 +46,6 @@ Gnulib checkout.  For example:
 $ ln -s $HOME/gnu/src/gnulib.git/gnulib-tool $HOME/bin/gnulib-tool
 @end example
-The home page for Gnulib is @url{http://www.gnu.org/software/gnulib}.
 @node git and CVS
 @section git and CVS
@@ -71,14 +69,7 @@ git resources:
 @item Overview:
 @item Homepage:
address@hidden Download:
address@hidden Tutorial:
address@hidden FAQ:
 @end table
When you use @code{git annotate} or @code{git blame} with Gnulib, it's
@@ -91,18 +82,19 @@ CVS checkouts are also supported:
 $ cvs -d :pserver:anonymous@@pserver.git.sv.gnu.org:/gnulib.git co -d gnulib 
 @end example
-Gnulib is hosted on @samp{savannah.gnu.org}. The project page is
 @node Keeping Up-to-date
 @section Keeping Up-to-date
The best way to work with Gnulib is to check it out of git.
-Subscribing to the @email{bug-gnulib@@gnu.org} mailing list will help you to
-plan when to update your local copy of Gnulib (which you use to
-maintain your software) from git.  To synchronize, you can use @code{git pull},
+To synchronize, you can use @code{git pull},
 or @code{cvs update -dP} if you are still using CVS.
+Subscribing to the @email{bug-gnulib@@gnu.org} mailing list will help
+you to plan when to update your local copy of Gnulib (which you use to
+maintain your software) from git.  You can review the archives,
+subscribe, etc., via
 Sometimes, using an updated version of Gnulib will require you to use
 newer versions of GNU Automake or Autoconf.  You may find it helpful
 to join the autotools-announce mailing list to be advised of such
@@ -116,9 +108,7 @@ to have filled out an assignment form for a project that 
uses the
 module for that contribution to be accepted here.
If you have a piece of code that you would like to contribute, please
-email @email{bug-gnulib@@gnu.org}.  You can review the archives,
-subscribe, etc., via
+email @email{bug-gnulib@@gnu.org}.
Generally we are looking for files that fulfill at least one of the
 following requirements:
@@ -194,9 +184,9 @@ For vi (vim): Add these lines to your @file{$HOME/.vimrc} 
 set expandtab
 @end example
-For Makefile and ChangeLog files, compensate this by adding this to
-your @file{$HOME/.vim/after/indent/make.vim} and
address@hidden/.vim/after/indent/changelog.vim} files:
+For Makefile and ChangeLog files, compensate for this by adding this
+to your @file{$HOME/.vim/after/indent/make.vim} file, and similarly
+for your @file{$HOME/.vim/after/indent/changelog.vim} file:
 " Use tabs for indentation, regardless of the global setting.
@@ -415,18 +405,3 @@ break.  This means that before any change can be committed 
to the
 repository, a test suite program must be produced that exposes the bug
 for regression testing.  All experimental work should be done on
 branches to help promote this.
address@hidden This copyright notice applies to this file.
address@hidden Generate it as output too, if the file is being formatted by 
address@hidden Otherwise, it should be formatted as part of a larger document
address@hidden that contains the relevant copyright notice.
address@hidden standalone
-Copyright @copyright{} 2001, 2003--2012 Free Software Foundation, Inc.
-Permission is granted to copy, distribute and/or modify this document
-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, with no Front-Cover Texts, and with no Back-Cover
-Texts.  A copy of the license is included in the ``GNU Free
-Documentation License'' file as part of this distribution.
address@hidden ifset

reply via email to

[Prev in Thread] Current Thread [Next in Thread]