OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Michael Schloh
  Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-web                      Date:   22-Jun-2005 18:00:09
  Branch: HEAD                             Handle: 2005062217000800

  Modified files:
    openpkg-web             security.wml

  Log:
    remove table of contents header to merge with main security secition, and
    introduce small refinements

  Summary:
    Revision    Changes     Path
    1.132       +2  -7      openpkg-web/security.wml
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-web/security.wml
  ============================================================================
  $ cvs diff -u -r1.131 -r1.132 security.wml
  --- openpkg-web/security.wml  22 Jun 2005 08:25:25 -0000      1.131
  +++ openpkg-web/security.wml  22 Jun 2005 16:00:08 -0000      1.132
  @@ -13,21 +13,16 @@
   OpenPKG's state of security with respect to the problems which could
   potentially affect an OpenPKG installation.
   
  -<a name="toc">
  -<h2>Page Contents</h2>
  -</a>
  -
   <ul>
      <li><a href="#top">Security (top of page)</a></li>
  -   <li><a href="#toc">Page Contents</a></li>
  -   <li><a href="#notifications">Security Incident Notifications</a></li>
  +   <li><a href="#notifications">Reporting of Incidents</a></li>
      <li><a href="#policies">Security Policies</a></li>
      <li><a href="#advisories">Security Advisories</a></li>
      <li><a href="#signature">Digital Signatures</a></li>
   </ul>
   
   <a name="notifications">
  -<h2>Security Incident Notifications</h2>
  +<h2>Reporting of Incidents</h2>
   </a>
   
   <p>
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to