Hello, is a fix-release for 1.65 possible? It seams that the fixes that were too late to get merged into 1.65 are need to prevent segfaults in 1.65. Oliver
2017-08-24 18:34 GMT+02:00 Владислав Щапов via Boost <boost@lists.boost.org> :
Hello,
Please, send links to commits.
boost.context: - https://github.com/boostorg/context/commit/420554fe9ac01482990e8ae314f4f7 ba81010c9a boost.fiber: - https://github.com/boostorg/fiber/commit/63f1041f0e484e64dec437a0fa780e a2463abda2
On 08/25/17 10:30, Oliver Kowalke via Boost wrote:
By making a PR to https://github.com/boostorg/website/blob/master/feed/history/boost_1_65_0.qb....
aren't they final now?
You can explicitly ask Daniel to re-generate release notes on the website. Since he'll probably see the PR, you can ask him in the PR.
On 08/25/17 11:00, Andrey Semashev wrote:
For an example, see https://github.com/boostorg/website/blob/master/feed/history/boost_1_59_0.qb... I added a note about a known issue in Boost.Log.
participants (3)
-
Andrey Semashev -
Oliver Kowalke -
Владислав Щапов