gnustandards-commit
[Top][All Lists]
Advanced

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

gnustandards ChangeLog standards.texi


From: Karl Berry
Subject: gnustandards ChangeLog standards.texi
Date: Fri, 06 Apr 2012 23:34:07 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       12/04/06 23:34:07

Modified files:
        .              : ChangeLog standards.texi 

Log message:
        gender neutralize

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.158&r2=1.159
http://cvs.savannah.gnu.org/viewcvs/gnustandards/standards.texi?cvsroot=gnustandards&r1=1.214&r2=1.215

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.158
retrieving revision 1.159
diff -u -b -r1.158 -r1.159
--- ChangeLog   6 Apr 2012 23:22:05 -0000       1.158
+++ ChangeLog   6 Apr 2012 23:34:07 -0000       1.159
@@ -1,5 +1,7 @@
 2012-04-06  Karl Berry  <address@hidden>
 
+       * standards.texi (Comments): Gender neutralize.
+
        * maintain.texi (Copyright Papers): five business days for
        the FSF to answer initially.  Information from johns.
 

Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.214
retrieving revision 1.215
diff -u -b -r1.214 -r1.215
--- standards.texi      11 Mar 2012 00:25:31 -0000      1.214
+++ standards.texi      6 Apr 2012 23:34:07 -0000       1.215
@@ -3,7 +3,7 @@
 @setfilename standards.info
 @settitle GNU Coding Standards
 @c This date is automagically updated when you save this file:
address@hidden lastupdate March 8, 2012
address@hidden lastupdate April 6, 2012
 @c %**end of header
 
 @dircategory GNU organization
@@ -2576,7 +2576,7 @@
 number NODE_NUM'' rather than ``an inode''.
 
 There is usually no purpose in restating the name of the function in
-the comment before it, because the reader can see that for himself.
+the comment before it, because readers can see that for themselves.
 There might be an exception when the comment is so long that the function
 itself would be off the bottom of the screen.
 



reply via email to

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