jakarta-site-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject cvs commit: jakarta-site2/docs/site dirlayout.html
Date Wed, 18 Apr 2001 21:15:24 GMT
ceki        01/04/18 14:15:24

  Modified:    xdocs/site dirlayout.xml
               docs/site dirlayout.html
  Log:
  Minor corrections.
  
  Revision  Changes    Path
  1.8       +11 -10    jakarta-site2/xdocs/site/dirlayout.xml
  
  Index: dirlayout.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/xdocs/site/dirlayout.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- dirlayout.xml	2001/03/21 09:23:14	1.7
  +++ dirlayout.xml	2001/04/18 21:15:24	1.8
  @@ -108,15 +108,16 @@
    <td>docs/ or www/</td>
    <td>Web site documentation.</td>
   
  - <td>Some projects choose to check in documentation for their website 
  - to ease maintanence of site. This may be a superset of the documentation
  - included in the documentation provided in distributions. If the project
  - includes regular distributions then the website should be an image of 
  - documentation of last release. For projects that don't have regular releases
  - and whos website does not have highly volatile information (news, bug reports 
  - etc.) then it is acceptable to use docs/ subdirectory otherwise the www/ directory
  - is recomended. Once checked into the CVS it is expected that the documentation will
  - also be checked out on live website.
  + <td>Some projects choose to check in documentation for their website
  + to ease maintanence of site. This may be a superset of the
  + documentation included in the documentation provided in
  + distributions. If the project includes regular distributions then the
  + website should be an image of documentation of last release. For
  + projects that don't have regular releases and whos website does not
  + have highly volatile information (news, bug reports etc.) then it is
  + acceptable to use docs/ subdirectory otherwise the www/ directory is
  + recomended. Once checked into the CVS it is expected that the
  + documentation will also be checked out on live website.
    </td>
    <td>YES</td>
    </tr>
  @@ -282,7 +283,7 @@
   
   <p>When adding binary files to CVS, the -kb option is automatically
    used for common binary types. See the
  - <code>CVSROOT/cvswrappers</code> file for the exact types.
  + <code>/home/cvs/CVSROOT/cvswrappers</code> file for the exact types.
   </p>
   
   </section>
  
  
  
  1.13      +11 -10    jakarta-site2/docs/site/dirlayout.html
  
  Index: dirlayout.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/docs/site/dirlayout.html,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- dirlayout.html	2001/04/03 06:41:01	1.12
  +++ dirlayout.html	2001/04/18 21:15:24	1.13
  @@ -309,15 +309,16 @@
   </td>
                                   <td bgcolor="#a0ddf0" colspan="" rowspan="" valign="top"
align="left">
       <font color="#000000" size="-1" face="arial,helvetica,sanserif">
  -                Some projects choose to check in documentation for their website 
  - to ease maintanence of site. This may be a superset of the documentation
  - included in the documentation provided in distributions. If the project
  - includes regular distributions then the website should be an image of 
  - documentation of last release. For projects that don't have regular releases
  - and whos website does not have highly volatile information (news, bug reports 
  - etc.) then it is acceptable to use docs/ subdirectory otherwise the www/ directory
  - is recomended. Once checked into the CVS it is expected that the documentation will
  - also be checked out on live website.
  +                Some projects choose to check in documentation for their website
  + to ease maintanence of site. This may be a superset of the
  + documentation included in the documentation provided in
  + distributions. If the project includes regular distributions then the
  + website should be an image of documentation of last release. For
  + projects that don't have regular releases and whos website does not
  + have highly volatile information (news, bug reports etc.) then it is
  + acceptable to use docs/ subdirectory otherwise the www/ directory is
  + recomended. Once checked into the CVS it is expected that the
  + documentation will also be checked out on live website.
    
               </font>
   </td>
  @@ -642,7 +643,7 @@
   </p>
                                                   <p>When adding binary files to CVS,
the -kb option is automatically
    used for common binary types. See the
  - <code>CVSROOT/cvswrappers</code> file for the exact types.
  + <code>/home/cvs/CVSROOT/cvswrappers</code> file for the exact types.
   </p>
                               </blockquote>
         </td></tr>
  
  
  

Mime
View raw message