$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [thread] Reducing the number of open tickets.
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2012-01-03 12:28:39
Le 29/12/11 15:26, Vicente J. Botet Escriba a écrit :
> Le 17/12/11 15:35, Vicente J. Botet Escriba a écrit :
>> Le 05/12/11 12:02, Anthony Williams a écrit :
>>> On 04/12/11 23:56, Vicente J. Botet Escriba wrote:
>>>> Le 03/12/11 18:23, Vicente J. Botet Escriba a écrit :
>>>
>>>> Anthony, please take a look at them and merge whatever you consider is
>>>> good after the testers have the time to take them in account (not
>>>> before
>>>> the 12/12/2011)
>>>
>>> Thanks for doing this Vicente. I will take a look when the tests
>>> have cycled, and merge them to release.
>>>
>> Any news on that?
>>
>> Best,
>> Vicente
>>
>> _______________________________________________
>> Unsubscribe & other changes:
>> http://listarchives.boost.org/mailman/listinfo.cgi/boost
>>
> Anthony, I would like to continue committing other patch for other
> tickets,
>
> #5351 <https://svn.boost.org/trac/boost/ticket/5351> interrupt a
> future get boost::unknown_exception
> <https://svn.boost.org/trac/boost/ticket/5351>
> #5990 <https://svn.boost.org/trac/boost/ticket/5990>
> shared_future<T>::get() has wrong return type
> <https://svn.boost.org/trac/boost/ticket/5990>
> #6174 <https://svn.boost.org/trac/boost/ticket/6174> packaged_task
> doesn't correctly handle moving results
> <https://svn.boost.org/trac/boost/ticket/6174>
> #5516 <https://svn.boost.org/trac/boost/ticket/5516> Upgrade lock is
> not acquired when previous upgrade lock releases if another read lock
> is present <https://svn.boost.org/trac/boost/ticket/5516>
>
> Part of #6195 <https://svn.boost.org/trac/boost/ticket/6195> c++11
> compliance: Provide the standard time related interface using
> Boost.Chrono <https://svn.boost.org/trac/boost/ticket/6195>
>
> but I would prefer if you merge before the current state on trunk.
> The date limit to merge to release for 1.49 is very close. If you have
> no time to do the merge I could do it, but I really prefer that you do
> it so that the modifications are inspected.
>
> Please, let me know.
>
Anthony,
I guess you are very busy, so I will merge to release, so that I will
continue the work on the trunk.
Let me know if you find something wrong.
Best,
Vicente