Re: cvs commit: apache-1.3/htdocs/manual new_features_1_3.html upgrading_to_1_3.html

[Marc Slemko <ma...@znep.com>]

On 22 Oct 1998 coar@hyperreal.org wrote:

> coar        98/10/22 14:14:45
> 
>   Modified:    htdocs/manual new_features_1_3.html upgrading_to_1_3.html
>   Log:
>   	Add the One True Config File stuff to the new/upgrade notes.
>   
>   Revision  Changes    Path
>   1.75      +12 -0     apache-1.3/htdocs/manual/new_features_1_3.html
>   
>   Index: new_features_1_3.html
>   ===================================================================
>   RCS file: /export/home/cvs/apache-1.3/htdocs/manual/new_features_1_3.html,v
>   retrieving revision 1.74
>   retrieving revision 1.75
>   diff -u -r1.74 -r1.75
>   --- new_features_1_3.html	1998/10/06 19:54:00	1.74
>   +++ new_features_1_3.html	1998/10/22 21:14:43	1.75
>   @@ -125,6 +125,18 @@
>    <H2><A NAME="config">Configuration Enhancements</A></H2>
>    
>    <DL>
>   +<DT><STRONG>Unified Server Configuration Files</STRONG></DT>
>   +<DD>As of the release following Apache 1.3.3, the contents of the three

Why not just say 1.3.4?  It seems much cleaner  than "the release
following 1.3.3".

Re: cvs commit: apache-1.3/htdocs/manual new_features_1_3.html upgrading_to_1_3.html

[Rodent of Unusual Size <Ke...@Golux.Com>]

Marc Slemko wrote:
> 
> Why not just say 1.3.4?  It seems much cleaner  than "the release
> following 1.3.3".

Just caution.  There have been a couple of times :-) when a
particular release didn't get .. um.. released.  And people
reading these docs might think, "Whoa!  1.3.4 is out already!"

Not a strong conviction; if you want me to change it, no
problem.

#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://Web.Golux.Com/coar/ASFD/>