Boost logo

Boost :

Subject: Re: [boost] [1.47.0] Any remaining showstoppers?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2011-07-07 09:23:05

On Thu, Jul 7, 2011 at 8:18 AM, Beman Dawes <bdawes_at_[hidden]> wrote:
> On Tue, Jul 5, 2011 at 5:21 PM, Eric Niebler <eric_at_[hidden]> wrote:
>> On 7/5/2011 12:43 PM, Emil Dotchevski wrote:
>>> On Tue, Jul 5, 2011 at 11:57 AM, Adam Merz <adammerz_at_[hidden]> wrote:
>>>>> Are there any other merges ready to go that still need permission to merge?
>>>> I don't know that it's a 'showstopper' per se, but the issue reported here [1]
>>>> is still present in boost-windows-2011-07-04.7z downloaded from
>>>>  [1]
>>> A few days ago I posted a patch file that fixes this problem, someone
>>> needs to apply it to the release branch.
>> Posted where? Has it been committed to trunk? Are the tests passing?
>>> I'm attaching the patch to this post as well.
>> It typically works like this: things are fixed on trunk. When the tests
>> are passing there, the library maintainer asks a release manager for
>> permission to merge to release, and they include a URL to the changeset
>> they would like to merge.
>> Are you asking for permission to merge? Can you send a URL?
> There has been no reply to Eric's query above:-(
> I'll see if I can reproduce the problem and test the patch.

I'm not able to reproduce this problem on either the current trunk or
branches/release. Thus I'm unwilling to apply the patch.

I'm building release candidates now. Once those go up on the ftp site,
perhaps the OP could try again. And if it fails, give us the exact
build command line that is failing.


Boost list run by bdawes at, gregod at, cpdaniel at, john at