Boost C++ Libraries: Ticket #7912: boost:thread documentation for 1.50 does not mention BOOST_THREAD_WAIT_BUG

owner, component changed

anonymous — Sun, 10 Feb 2013 21:44:00 GMT

owner changed from Matias Capeletto to Anthony Williams
component Documentation → thread

viboes — Sun, 10 Feb 2013 22:00:24 GMT

I don't remember which problem BOOST_THREAD_WAIT_BUG tried to fix. Currently this is not used any more. If you know of a problem please, be free to signal it here.

owner, status changed

viboes — Sun, 10 Feb 2013 22:01:09 GMT

owner changed from Anthony Williams to viboes
status new → assigned

anonymous — Wed, 13 Feb 2013 07:48:54 GMT

BOOST_THREAD_WAIT_BUG was a workaround for the ticket 6130, which describes some strange OS problem. If possible, please remove the workaround from 1.50 issue/branch (and where else it has been applied), it breaks the functionality.

status changed; resolution set

viboes — Wed, 13 Feb 2013 21:22:45 GMT

status assigned → closed
resolution → worksforme

Replying to anonymous:

BOOST_THREAD_WAIT_BUG was a workaround for the ticket #6130, which describes some strange OS problem. If possible, please remove the workaround from 1.50 issue/branch (and where else it has been applied), it breaks the functionality.

Thanks for the ticket number. What do you mean by "remove the workaround from 1.50 issue/branch"? Boost doesn't maintain specific release branches.

status, component changed; resolution deleted

anonymous — Thu, 14 Feb 2013 07:40:27 GMT

status closed → reopened
resolution worksforme
component thread → Documentation

I mean the people, which distribution happens to have 1.50 release should be aware, that the mentioned functionality is broken in this release. That's why the problem report was filed agains documentation.

viboes — Fri, 15 Feb 2013 17:43:54 GMT

Replying to anonymous:

I mean the people, which distribution happens to have 1.50 release should be aware, that the mentioned functionality is broken in this release. That's why the problem report was filed agains documentation.

Thanks for the clarification. I didn't know that the documentation for a release could be updated.

component changed

anonymous — Mon, 01 Apr 2013 19:08:49 GMT

component Documentation → thread

Bugs in a library's documentation should be filed against the library, not Documentation. 'Documentation' is for general documentation bugs.

If you want to update website documentation, you need to add files to the appropriate location under https://svn.boost.org/svn/boost/website/public_html/live/doc/fixes/

cc set

Daniel James — Mon, 01 Apr 2013 20:34:17 GMT

cc dnljms@… added

viboes — Mon, 01 Apr 2013 22:05:42 GMT

Replying to anonymous:

Bugs in a library's documentation should be filed against the library, not Documentation. 'Documentation' is for general documentation bugs.

If you want to update website documentation, you need to add files to the appropriate location under https://svn.boost.org/svn/boost/website/public_html/live/doc/fixes/

I didn't know that we could add patches to the library documentation. Please, could you point me to a link where the procedure is explained? Should I generate the html documentation or it is enough to provide the qbk and Jamfile files?

Daniel James — Mon, 01 Apr 2013 22:37:53 GMT

It isn't explained anywhere because I make it up as I go along. Maintaining documentation would be too much work. Basically, I have a directory on the website (the fixes directory I linked to), and if you place a html file in the appropriate location within it, it will be served instead of the one from the distribution. If you look in the directory I linked to, the layout should be obvious. But if you get it wrong, I'll fix it up.

But if that's too hard for you, can you let me know what you want to change (giving full text).

status changed

viboes — Sun, 09 Jun 2013 20:12:02 GMT

status reopened → new

status changed

viboes — Sun, 09 Jun 2013 20:12:37 GMT

status new → assigned