$include_dir="/home/hyper-archives/boost-commit/include"; include("$include_dir/msg-header.inc") ?>
From: daniel_james_at_[hidden]
Date: 2008-02-10 14:57:34
Author: danieljames
Date: 2008-02-10 14:57:34 EST (Sun, 10 Feb 2008)
New Revision: 43218
URL: http://svn.boost.org/trac/boost/changeset/43218
Log:
Fix the links in the 'more' index page.
Text files modified: 
   branches/fix-links/more/index.htm |    50 ++++++++++++++++++++--------------------
   1 files changed, 25 insertions(+), 25 deletions(-)
Modified: branches/fix-links/more/index.htm
==============================================================================
--- branches/fix-links/more/index.htm	(original)
+++ branches/fix-links/more/index.htm	2008-02-10 14:57:34 EST (Sun, 10 Feb 2008)
@@ -15,78 +15,78 @@
             <td>Home</td>
             <td>Libraries</td>
             <td>People</td>
-            <td>FAQ</td>
+            <td>FAQ</td>
             <td>More</td>
          </tr>
       </table>
       <h1>More Information</h1>
       <h2>Boost Policies</h2>
       <blockquote>
-         <p>Mailing List Discussion Policy.  
+         <p>Mailing List Discussion Policy.  
             What's acceptable and what isn't.</p>
-         <p>Library Requirements and Guidelines.  
+         <p>Library Requirements and Guidelines.  
             Basic standards for those preparing a submission.</p>
-         <P><A href="separate_compilation.html"><STRONG>Guidelines for Libraries with Separate 
+         <P><A href="http://www.boost.org/more/separate_compilation.html"><STRONG>Guidelines for Libraries with Separate 
                   Source</STRONG></A>.  Basic tutorial for libraries that require the 
             building of a separate link library.</P>
          <p>Writing Documentation for Boost
             Basic guidelines for writing documentation and templates for quickly generating 
             documentation that follows the guidelines.</p>
-         <p>Test Policy and Protocols.  How 
+         <p>Test Policy and Protocols.  How 
             testing works at Boost.</p>
-         <p>Library Submission Process.  
+         <p>Library Submission Process.  
             How to submit a library to Boost.</p>
-         <p>Library Formal Review Process. 
+         <p>Library Formal Review Process. 
             Including how to submit a review comment.</p>
-         <p>Header Policy.  Headers are where a 
+         <p>Header Policy.  Headers are where a 
             library contacts its users, so programming practices are particularly 
             important.</p>
-         <p>Library Reuse.  Should Boost 
+         <p>Library Reuse.  Should Boost 
             libraries use other boost libraries?  What about the C++ Standard 
             Library?  It's another trade-off.</p>
-         <p><b>Moderators</b>.  Who they are and what 
+         <p><b>Moderators</b>.  Who they are and what 
             they do.</p>
       </blockquote>
       <h2>Boost Whatever</h2>
       <blockquote>
-         <p><b>License Information </b> Information 
+         <p><b>License Information </b> Information 
             about the Boost Software License.</p>
-         <p><b>Bibliography </b> Print and online 
+         <p><b>Bibliography </b> Print and online 
             publications relating to Boost and Boost libraries.</p>
          <p><b>Who's Using Boost? </b> 
          Products and organisations that are using Boost.</p>
          <p>Compiler Status  Describes 
             what library works with which compiler.</p>
-         <p><b>Links</b>  Links of special interest to Boost 
+         <p><b>Links</b>  Links of special interest to Boost 
             users.</p>
-         <p><b>Formal Review Schedule</b>  
+         <p><b>Formal Review Schedule</b>  
             Future, current, and recently past Formal Reviews.</p>
-         <p><b>Release Procedures</b>  How 
+         <p><b>Release Procedures</b>  How 
             developers and the release manager prepare for a Boost release.</p>
-         <p><b>Updating the Website</b>  How 
+         <p><b>Updating the Website</b>  How 
             developers can update the Boost website between releases.</p>
-         <p>Internal Regression Test Suite   
+         <p>Internal Regression Test Suite   
             Describes the tool for generating the compiler status tables
          </p>
-         <p><b>Proposal for a C++ Library Repository Web Site</b>  
+         <p><b>Proposal for a C++ Library Repository Web Site</b>  
             The original 1998 proposal that launched Boost.</p>
-         <p><b>How to report bugs</b>  Ways to report Boost 
+         <p><b>How to report bugs</b>  Ways to report Boost 
             bugs.</p>
-         <p><b>How to request features</b> Ways 
+         <p><b>How to request features</b> Ways 
             to request new library features.</p>
-         <p><b><a href="boost_soc_06_overview.html">An overview of Boost participation in
+         <p><b><a href="http://www.boost.org/more/boost_soc_06_overview.html">An overview of Boost participation in
             Google Summer of Code™ 2006</a></b> A report of our first experience
             in this open source initiative.</p>
-         <p><b>Version History</b> Changes 
+         <p><b>Version History</b> Changes 
          and additions in past Boost releases.</p>
       </blockquote>
       <h2>Articles and Papers</h2>
       <blockquote>
-         <p>Portability Hints: Borland C++ 5.5.1 describes 
+         <p>Portability Hints: Borland C++ 5.5.1 describes 
             Borland C++ portability issues, with suggested workarounds.</p>
-         <p>Portability Hints: Microsoft VC++ 6.0 SP4
+         <p>Portability Hints: Microsoft VC++ 6.0 SP4
             describes Microsoft C++ portability issues, with suggested workarounds.</p>
-         <p><a href="int_const_guidelines.htm"><strong>Coding Guidelines for Integral Constant 
+         <p><a href="http://www.boost.org/more/int_const_guidelines.htm"><strong>Coding Guidelines for Integral Constant 
                   Expressions</strong></a> describes how to work through the maze of 
             compiler related bugs surrounding this tricky topic.</p>
       </blockquote>