findutils-patches
[Top][All Lists]
Advanced

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

Re: [Findutils-patches] Re: release dates in NEWS


From: Eric Blake
Subject: Re: [Findutils-patches] Re: release dates in NEWS
Date: Thu, 19 Jul 2007 21:23:25 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666

According to James Youngman on 7/19/2007 3:52 PM:
>>         * doc/find-maint.texi (Documentation): Document where release
>>         dates are usefully recorded.
> 
> The actual changes to that file are lengthy and not mentioned here.
> Would you be able to work on the ChangeLog entry a bit?

Bah - my editor ate all the trailing whitespace (since it doesn't affect
the output of correct .texi files), but I didn't notice that it made the
diff that much bigger before I had already checked it in.  The actual
change, minus whitespace, was:

Index: doc/find-maint.texi
===================================================================
RCS file: /sources/findutils/findutils/doc/find-maint.texi,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -b -r1.2 -r1.3
--- doc/find-maint.texi 2 Jul 2007 08:25:42 -0000       1.2
+++ doc/find-maint.texi 18 Jul 2007 03:40:46 -0000      1.3
@@ -660,6 +660,7 @@ Mainly obsolete.
 @item NEWS
 Enumerates the user-visible change in each release.  Typical changes
 are fixed bugs, functionality changes and documentation changes.
+Include the date when a release is made.
 @item ChangeLog
 This file enumerates all changes to the findutils source code (with
 the possible exception of @file{.cvsignore} and @code{.gitignore}
@@ -669,7 +670,7 @@ If a change fixes a bug, always give the
 the @file{ChangeLog} and @file{NEWS} files and of course also in the
 checkin message.  In general, it should be possible to enumerate all
 material changes to a function by searching for its name in
address@hidden
address@hidden  Mention when each release is made.
 @end table

 @node Testing

Meanwhile, I'll edit the ChangeLog entry to mention that I (well, my
editor) ate all the trailing whitespace.

-- 
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden




reply via email to

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