Re: [boost] [release] 1.64.0 post-beta merges

2017-04-09 14:28 GMT+02:00 Daniel James via Boost :

On 9 April 2017 at 13:20, Oliver Kowalke via Boost wrote:

...

2017-03-24 2:00 GMT+01:00 Rene Rivera via Boost :

...

The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See < https://github.com/boostorg/boost/wiki/Release-Beta-Merge-Policy>

Do I get permission to update the documentation? I could revert the last commit and update only the documentation so that the users get a hint how to choose the appropriate API.

Documentation changes are fine, but Rene's suggestions shouldn't be too hard to implement,

maybe I misunderstood the last comments - is it sufficient to keep execution _context.hpp unmodified (no code clean-up) and extending the definition of property context-switch to values "cc ec ec1 ec2" to get permission to merge the commit into master?