On 5/5/19 3:06 PM, Vinnie Falco via Boost wrote:
On Sun, May 5, 2019 at 2:12 AM Richard Hodges via Boost
wrote: If there is any way of getting a patch release out into the wild as a complete tar.gz that would be helpful as it would mean I don't have to redefine my build environment in terms of git submodules.
Changes to the Beast in Boost 1.70 for the fix can be obtained from this branch:
https://github.com/boostorg/beast/commits/v248-hf1
you can retrieve a patch from github using this URI format:
https://github.com/boostorg/beast/compare/boost-1.70.0...v248-hf1.diff
The fix has also been merged to master and develop:
One thing you could do to aid 1.70 users is to create a PR for 1.70 release notes[1], adding a note about the problem with a link to the patch/commit that fixes it. You can look in past release notes for examples, we've had multiple occasions of such notes. [1]: https://github.com/boostorg/website/blob/master/feed/history/boost_1_70_0.qb...