Deleted - explicit failure for teststreams and VC8.0

          this problem was fixed in RCS file:
          /cvsroot/boost/boost/boost/date_time/posix_time/time_formatters.hpp,v
          revision 1.11.4.1
the rest of the changes seem to have to do with my editor removing trailing blanks from lines


[SVN r26374]

status/explicit-failures-markup.xml

@@ -342,15 +342,6 @@
                 <note author="B. Garst" refid="18,19,20"/>
             </mark-failure>
         </test>
-        <test name="teststreams">
-            <mark-failure>
-                <toolset name="vc-8_0"/>
-                <note author="Aleksey Gurtovoy">
-                    The test terminates at run-time due what appears to be a bug
-                    in the standard library implementation.
-                </note>
-            </mark-failure>
-        </test>
         <test name="testdate_dll">
             <mark-failure>
                 <toolset name="gcc-2.95.3-stlport-4.5.3-linux"/>
@@ -408,7 +399,7 @@
         <mark-unusable>
             <toolset name="iw-7_1*"/>
             <note author="Aleksey Gurtovoy">
-                The failure is caused by a standard library bug: the 
+                The failure is caused by a standard library bug: the
                 iostream components fail to handle <code>ios::internal</code>
                 flag.
             </note>
@@ -583,7 +574,7 @@
             <toolset name="borland-5_5_1"/>
             <note author="Alisdair Meredith" date="30 Jan 2004">
                 <p>
-                This library has never worked [on Borland 5.5.1 and 5.6.4], and the only tests 
+                This library has never worked [on Borland 5.5.1 and 5.6.4], and the only tests
                 that 'pass' are compile-fail tests failing for the wrong reasons!
                 </p>
             </note>
@@ -871,20 +862,20 @@ for more information.
             <toolset name="iw-7_1-vc6"/>
             <note author="Aleksey Gurtovoy" refid="29"/>
         </mark-expected-failures>
-        <mark-expected-failures reason="?">        
+        <mark-expected-failures reason="?">
             <test name="test_class_info_load_text_warchive"/>
             <toolset name="intel-win32-8_0"/>
-            <note author="Aleksey Gurtovoy" refid="29"/>            
+            <note author="Aleksey Gurtovoy" refid="29"/>
         </mark-expected-failures>
-        <mark-expected-failures reason="?">        
+        <mark-expected-failures reason="?">
             <test name="test_smart_cast"/>
             <toolset name="intel-7.1-linux"/>
-            <note author="Aleksey Gurtovoy" refid="29"/>            
+            <note author="Aleksey Gurtovoy" refid="29"/>
         </mark-expected-failures>
-        <mark-expected-failures reason="?">        
+        <mark-expected-failures reason="?">
             <test name="test_class_info_load_*"/>
             <toolset name="intel-8.0-linux"/>
-            <note author="Aleksey Gurtovoy" refid="29"/>            
+            <note author="Aleksey Gurtovoy" refid="29"/>
         </mark-expected-failures>
     </library>
 
@@ -1478,10 +1469,10 @@ for more information.
             <toolset name="intel-7.1-linux"/>
             <toolset name="intel-8.0-linux"/>
             <note author="Aleksey Gurtovoy">
-                The library is <a href="http://article.gmane.org/gmane.comp.lib.boost.devel/110420">known to work</a> 
-                in this configuration. The failures are due to configuration issues of 
-                the particular testing environment these tests have been run in. The 
-                regression runners and library developers are aware of the problem and 
+                The library is <a href="http://article.gmane.org/gmane.comp.lib.boost.devel/110420">known to work</a>
+                in this configuration. The failures are due to configuration issues of
+                the particular testing environment these tests have been run in. The
+                regression runners and library developers are aware of the problem and
                 plan to fix it for the next release.
             </note>
         </mark-expected-failures>
@@ -1496,8 +1487,8 @@ for more information.
             <test name="pickle4"/>
             <toolset name="gcc-3.4.2-linux"/>
             <note author="Aleksey Gurtovoy">
-                The test is <a href="http://article.gmane.org/gmane.comp.lib.boost.devel/110671">known to work</a> 
-                in this configuration. The failures are due to configuration issues of 
+                The test is <a href="http://article.gmane.org/gmane.comp.lib.boost.devel/110671">known to work</a>
+                in this configuration. The failures are due to configuration issues of
                 the particular testing environment these tests have been run in.
             </note>
         </mark-expected-failures>
@@ -1816,7 +1807,7 @@ for more information.
                 <note author="Aleksey Gurtovoy">
                     This functionality is available only on compilers that implement C++ Core Language
                     <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#337">Defect Report 337</a>.
-                </note>        
+                </note>
             </mark-failure>
         </test>
     </library>
@@ -2007,7 +1998,7 @@ for more information.
     <note id="25">
       The failure is caused by a runtime limitation. Locale support is only
       available with the static linked variant of the runtime. Generally
-      the dynamic linked variant is required when building dynamic modules, 
+      the dynamic linked variant is required when building dynamic modules,
       DLL, <code>so</code>, etc.
     </note>
 
@@ -2022,13 +2013,13 @@ for more information.
     </note>
 
     <note id="28">
-        Unresearched failure, please contact library developers for more 
+        Unresearched failure, please contact library developers for more
         information about possible causes.
     </note>
 
     <note id="29">
         The test fails due to unresearched issues. The library
-        developers are aware of this failure, but need help with 
+        developers are aware of this failure, but need help with
         investigating/addressing it for future releases.
     </note>