Boost logo

Boost-Commit :

Subject: [Boost-commit] svn:boost r77311 - in trunk/libs/config/doc: . html
From: mimomorin_at_[hidden]
Date: 2012-03-11 20:31:51


Author: michel
Date: 2012-03-11 20:31:50 EDT (Sun, 11 Mar 2012)
New Revision: 77311
URL: http://svn.boost.org/trac/boost/changeset/77311

Log:
Minor documentation fix
Text files modified:
   trunk/libs/config/doc/configuring_boost.qbk | 8 ++++----
   trunk/libs/config/doc/html/index.html | 14 +++++++-------
   2 files changed, 11 insertions(+), 11 deletions(-)

Modified: trunk/libs/config/doc/configuring_boost.qbk
==============================================================================
--- trunk/libs/config/doc/configuring_boost.qbk (original)
+++ trunk/libs/config/doc/configuring_boost.qbk 2012-03-11 20:31:50 EDT (Sun, 11 Mar 2012)
@@ -111,7 +111,7 @@
 the default user.hpp provided by boost. This option allows only one
 configure-generated setup; boost developers should avoid this option,
 as it incurs the danger of accidentally committing a configure-modified
-__BOOST_CONFIG_USER_HEADER__ to the cvs repository (something you will not
+__BOOST_CONFIG_USER_HEADER__ to the svn repository (something you will not
 be thanked for!).
 
 * [*Option 2:] give the header a more memorable name, and place it somewhere
@@ -237,7 +237,7 @@
 to look for in a dll rather than in a static library).
 Note that there may be some libraries that can only be statically linked
 (Boost.Test for example) and others which may only be dynamically linked
-(Boost.Threads for example), in these cases this macro has no effect.
+(Boost.Thread for example), in these cases this macro has no effect.
 ]]
 [[`BOOST_`['WHATEVER]`_DYN_LINK`][
 Forces library "whatever" to be linked as a dll rather than a static library
@@ -248,7 +248,7 @@
 which symbols to look for in a dll rather than in a static library).
 Note that there may be some libraries that can only be statically linked
 (Boost.Test for example) and others which may only be dynamically linked
-(Boost.Threads for example), in these cases this macro is unsupported.
+(Boost.Thread for example), in these cases this macro is unsupported.
 ]]
 [[`BOOST_ALL_NO_LIB`][
 Tells the config system not to automatically select which libraries to link
@@ -307,7 +307,7 @@
 
 The following usage examples represent just a few of the possibilities:
 
-[section Example 1, creating our own frozen configuration]
+[section Example 1: creating our own frozen configuration]
 
 Lets suppose that we're building boost with Visual C++ 6, and STLport 4.0. Lets
 suppose also that we don't intend to update our compiler or standard library

Modified: trunk/libs/config/doc/html/index.html
==============================================================================
--- trunk/libs/config/doc/html/index.html (original)
+++ trunk/libs/config/doc/html/index.html 2012-03-11 20:31:50 EDT (Sun, 11 Mar 2012)
@@ -298,7 +298,7 @@
             provided by boost. This option allows only one configure-generated setup;
             boost developers should avoid this option, as it incurs the danger of
             accidentally committing a configure-modified <boost/config/user.hpp>
- to the cvs repository (something you will not be thanked for!).
+ to the svn repository (something you will not be thanked for!).
           </li>
 <li class="listitem">
             <span class="bold"><strong>Option 2:</strong></span> give the header a more memorable
@@ -587,7 +587,7 @@
                   knows which symbols to look for in a dll rather than in a static
                   library). Note that there may be some libraries that can only be
                   statically linked (Boost.Test for example) and others which may
- only be dynamically linked (Boost.Threads for example), in these
+ only be dynamically linked (Boost.Thread for example), in these
                   cases this macro has no effect.
                 </p>
               </td>
@@ -609,7 +609,7 @@
                   knows which symbols to look for in a dll rather than in a static
                   library). Note that there may be some libraries that can only be
                   statically linked (Boost.Test for example) and others which may
- only be dynamically linked (Boost.Threads for example), in these
+ only be dynamically linked (Boost.Thread for example), in these
                   cases this macro is unsupported.
                 </p>
               </td>
@@ -686,7 +686,7 @@
 </h3></div></div></div>
 <div class="toc"><dl>
 <dt><span class="section"><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration">Example
- 1, creating our own frozen configuration</a></span></dt>
+ 1: creating our own frozen configuration</a></span></dt>
 <dt><span class="section"><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_2__skipping_files_that_you_don_t_need">Example
         2: skipping files that you don't need</a></span></dt>
 <dt><span class="section"><a href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_3__using_configure_script_to_freeze_the_boost_configuration">Example
@@ -725,8 +725,8 @@
       </p>
 <div class="section boost_config_configuring_boost_for_your_platform_advanced_configuration_usage_example_1__creating_our_own_frozen_configuration">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration" title="Example 1, creating our own frozen configuration">Example
- 1, creating our own frozen configuration</a>
+<a name="boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration"></a><a class="link" href="index.html#boost_config.configuring_boost_for_your_platform.advanced_configuration_usage.example_1__creating_our_own_frozen_configuration" title="Example 1: creating our own frozen configuration">Example
+ 1: creating our own frozen configuration</a>
 </h4></div></div></div>
 <p>
           Lets suppose that we're building boost with Visual C++ 6, and STLport 4.0.
@@ -951,7 +951,7 @@
 </div>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"><p><small>Last revised: March 10, 2012 at 18:02:52 GMT</small></p></td>
+<td align="left"><p><small>Last revised: March 12, 2012 at 00:24:44 GMT</small></p></td>
 <td align="right"><div class="copyright-footer"></div></td>
 </tr></table>
 <hr>


Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk