Known bug #64 fixed by Constantine Sapuntzakis and Joshua Kwan in 7.20.0

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 3982dc4ec8f07facaa8c828fad68d593f4a010c8..c38114141796c553cd2c29a4d2d382fc72aa9c15 100644 (file)
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -40,11 +40,6 @@ may have been fixed since this was written!
   properly wait for the connect to be confirmed. See test case 564 for a first
   shot at a test case.
 
-64. The threaded resolver used in libcurl on Windows has some kind of race
-  problem when multiple simultanoes resolves are done, like with the multi
-  interface transferring many files in parallell:
-  http://curl.haxx.se/mail/lib-2009-04/0028.html
-
 63. When CURLOPT_CONNECT_ONLY is used, the handle cannot reliably be re-used
   for any further requests or transfers. The work-around is then to close that
   handle with curl_easy_cleanup() and create a new. Some more details: