[release] 1.68.0 post-beta merges
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> The master branch will close for the 1.68.0 release on August 1st. -- Marshall
Hi guys, Hi Christophe, Am 11.07.2018 um 01:10 schrieb Marshall Clow 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>
Would it be possible to include the simple fix for Boost.MSM from pull-request #15 (https://github.com/boostorg/msm/pull/15)? That one fixes compilation of Boost.MSM with C++17. std::random_shuffle was removed from the standard-library and therefore needs to be conditionally handled in Boost.MSM. (That problem occurs with libc++ 6 for example.)
The master branch will close for the 1.68.0 release on August 1st.
-- Marshall
Thanks, Deniz
On Wed, Jul 11, 2018 at 3:14 AM, Deniz Bahadir via Boost < boost@lists.boost.org> wrote:
Hi guys, Hi Christophe,
Am 11.07.2018 um 01:10 schrieb Marshall Clow 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>
Would it be possible to include the simple fix for Boost.MSM from pull-request #15 (https://github.com/boostorg/msm/pull/15)?
That one fixes compilation of Boost.MSM with C++17. std::random_shuffle was removed from the standard-library and therefore needs to be conditionally handled in Boost.MSM. (That problem occurs with libc++ 6 for example.)
Has it been tested on develop? Are the tests passing? If so, yes. -- Marshall
Am 12.07.2018 um 22:26 schrieb Marshall Clow via Boost:
On Wed, Jul 11, 2018 at 3:14 AM, Deniz Bahadir via Boost < boost@lists.boost.org> wrote:
Hi guys, Hi Christophe,
Am 11.07.2018 um 01:10 schrieb Marshall Clow 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>
Would it be possible to include the simple fix for Boost.MSM from pull-request #15 (https://github.com/boostorg/msm/pull/15)?
That one fixes compilation of Boost.MSM with C++17. std::random_shuffle was removed from the standard-library and therefore needs to be conditionally handled in Boost.MSM. (That problem occurs with libc++ 6 for example.)
Has it been tested on develop? Are the tests passing?
I cannot tell. It is still a pull-request and not merged in the develop branch of Boost.MSM. Is there some way I can explicitly trigger testing that pull-request? (The automaticly startet Travis-tests all passed.) Note, that I am not the author/maintainer of Boost.MSM. I am just the one providing the pull-request and asking for it being included.
If so, yes.
That would be great. Deniz
Am 13.07.2018 um 08:16 schrieb Deniz Bahadir via Boost:
Am 12.07.2018 um 22:26 schrieb Marshall Clow via Boost:
On Wed, Jul 11, 2018 at 3:14 AM, Deniz Bahadir via Boost < boost@lists.boost.org> wrote:
Hi guys, Hi Christophe,
Am 11.07.2018 um 01:10 schrieb Marshall Clow 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>
Would it be possible to include the simple fix for Boost.MSM from pull-request #15 (https://github.com/boostorg/msm/pull/15)?
That one fixes compilation of Boost.MSM with C++17. std::random_shuffle was removed from the standard-library and therefore needs to be conditionally handled in Boost.MSM. (That problem occurs with libc++ 6 for example.)
Has it been tested on develop? Are the tests passing?
I cannot tell. It is still a pull-request and not merged in the develop branch of Boost.MSM. Is there some way I can explicitly trigger testing that pull-request? (The automatically started Travis-tests all passed.)
As I did not see any further reaction, neither on Github or via e-Mail, I assume this pull-request will not make it int the next Boost release!? So Boost.MSM needs local modifications if used in C++17 environment...
Note, that I am not the author/maintainer of Boost.MSM. I am just the one providing the pull-request and asking for it being included.
Is Christophe still active on Boost and still maintaining Boost.MSM? Or is anyone else maintaining it?
If so, yes.
That would be great.
Deniz
On 7/10/2018 7:10 PM, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
-- Marshall
I would like to merge the 'develop' branch changes of iostreams to 'master'. Can I do it now ?
On Wed, Jul 11, 2018 at 5:58 AM, Edward Diener via Boost < boost@lists.boost.org> wrote:
On 7/10/2018 7:10 PM, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
-- Marshall
I would like to merge the 'develop' branch changes of iostreams to 'master'. Can I do it now ?
If they are appropriate for post-beta (i.e, no major new features, etc), then yes. -- Marshall
On 7/12/2018 4:27 PM, Marshall Clow via Boost wrote:
On Wed, Jul 11, 2018 at 5:58 AM, Edward Diener via Boost < boost@lists.boost.org> wrote:
On 7/10/2018 7:10 PM, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
-- Marshall
I would like to merge the 'develop' branch changes of iostreams to 'master'. Can I do it now ?
If they are appropriate for post-beta (i.e, no major new features, etc), then yes.
Then I will wait until after the coming release since one of the changes to iostreams is adding the zstd compression/decompression filter, and that is definitely a new feature. I do not want to just cherry pick any of the other changes that came after it.
Hi Marshall Clow Via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I'd like to merge the following fixes: https://github.com/boostorg/geometry/pull/488/files https://github.com/boostorg/geometry/pull/499/files https://github.com/boostorg/geometry/commit/84d08d69362028ed6befa86ac5056b7d... https://github.com/boostorg/geometry/commit/ec7ac6df00195dbe7ba8802211827662... I'll also update release notes in the docs. Adam
On Wed, Jul 11, 2018 at 6:10 AM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Hi
Marshall Clow Via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I'd like to merge the following fixes:
https://github.com/boostorg/geometry/pull/488/files https://github.com/boostorg/geometry/pull/499/files https://github.com/boostorg/geometry/commit/84d08d69362028ed 6befa86ac5056b7d4001749d https://github.com/boostorg/geometry/commit/ec7ac6df00195dbe 7ba88022118276623cba972a
I'll also update release notes in the docs.
They look fine to me. -- Marshall
Marshall Clow Via Boost wrote:
On Wed, Jul 11, 2018 at 6:10 AM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Hi
Marshall Clow Via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I'd like to merge the following fixes:
https://github.com/boostorg/geometry/pull/488/files https://github.com/boostorg/geometry/pull/499/files https://github.com/boostorg/geometry/commit/84d08d69362028ed 6befa86ac5056b7d4001749d https://github.com/boostorg/geometry/commit/ec7ac6df00195dbe 7ba88022118276623cba972a
I'll also update release notes in the docs.
They look fine to me.
How about these two? https://github.com/boostorg/geometry/commit/1b3cab85bddbb4e6d76b9acf938182c3... https://github.com/boostorg/geometry/commit/01c7c4b6e93b498230133cb85f8240c8... I'd also like to move test files to different directories which is caused by switching from CircleCI 1.0 to 2.0. Would this be acceptable? https://github.com/awulkiew/geometry/commit/577688d238f3dbab987ad0e8e32e6be6... Adam
On Sun, Jul 22, 2018 at 12:48 PM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Marshall Clow Via Boost wrote:
On Wed, Jul 11, 2018 at 6:10 AM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Hi
Marshall Clow Via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I'd like to merge the following fixes:
https://github.com/boostorg/geometry/pull/488/files https://github.com/boostorg/geometry/pull/499/files https://github.com/boostorg/geometry/commit/84d08d69362028ed 6befa86ac5056b7d4001749d https://github.com/boostorg/geometry/commit/ec7ac6df00195dbe 7ba88022118276623cba972a
I'll also update release notes in the docs.
They look fine to me.
How about these two? https://github.com/boostorg/geometry/commit/1b3cab85bddbb4e6 d76b9acf938182c349417f17 https://github.com/boostorg/geometry/commit/01c7c4b6e93b4982 30133cb85f8240c833fe6853
If the tests are passing on develop, then those are both fine.
I'd also like to move test files to different directories which is caused by switching from CircleCI 1.0 to 2.0. Would this be acceptable? https://github.com/awulkiew/geometry/commit/577688d238f3dbab 987ad0e8e32e6be62b1f1188
Doesn't that need to go into develop first? -- Marshall
Marshall Clow Via Boost wrote:
On Sun, Jul 22, 2018 at 12:48 PM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
How about these two? https://github.com/boostorg/geometry/commit/1b3cab85bddbb4e6 d76b9acf938182c349417f17 https://github.com/boostorg/geometry/commit/01c7c4b6e93b4982 30133cb85f8240c833fe6853
If the tests are passing on develop, then those are both fine. Ok thanks.
I'd also like to move test files to different directories which is caused by switching from CircleCI 1.0 to 2.0. Would this be acceptable? https://github.com/awulkiew/geometry/commit/577688d238f3dbab 987ad0e8e32e6be62b1f1188
Doesn't that need to go into develop first?
Yes, I'm asking because I have to modify docs too so I want to know what I can do to avoid cherry picking commits. Adam
Hi Marshall, I'd like to merge bugfix for fusion, https://github.com/boostorg/fusion/pull/186 . Is it OK? Thanks, Kohei On 07/11/2018 08:10 AM, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
-- Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Sat, Jul 14, 2018 at 8:22 PM, Kohei Takahashi via Boost < boost@lists.boost.org> wrote:
Hi Marshall,
I'd like to merge bugfix for fusion, https://github.com/boostorg/fusion/pull/186 . Is it OK?
Sure. Thanks for asking. -- Marshall
Hi, I request permission to merge 228b20d ( https://github.com/boostorg/optional/commit/228b20df82fd5ac83f7e8bfebf2d5358... ). This fixes the regression in Boost.Optional that I added with the previous commit (71d797b9ee132b381c2d4f3b5bcca2078b0a5062) to 1.68. The fix is trivial (changes the order of declarations), have been in develop for 4 days and passing all tests. It also passes the Travis CI tests. Regards, &rzej; 2018-07-11 1:10 GMT+02:00 Marshall Clow via Boost <boost@lists.boost.org>:
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>
The master branch will close for the 1.68.0 release on August 1st.
-- Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/ mailman/listinfo.cgi/boost
On Mon, Jul 16, 2018 at 1:03 AM, Andrzej Krzemienski via Boost < boost@lists.boost.org> wrote:
Hi, I request permission to merge 228b20d ( https://github.com/boostorg/optional/commit/228b20df82fd5ac83f7e8bfebf2d53 58fd1c7f2a ). This fixes the regression in Boost.Optional that I added with the previous commit (71d797b9ee132b381c2d4f3b5bcca2078b0a5062) to 1.68. The fix is trivial (changes the order of declarations), have been in develop for 4 days and passing all tests. It also passes the Travis CI tests.
Approved. -- Marshall
On 07/11/18 02:10, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I would like to merge to Boost.Atomic master this commit: https://github.com/boostorg/atomic/commit/6e14ca24dab50ad4c1fa8c27c7dd6f1cb7... It fixes compilation with clang. Multiple gcc and clang testers have cycled and AppVeyor CI have passed. Travis CI have passed except for Boost.System errors that I mentioned in a recent post.
On Wed, Jul 18, 2018 at 2:55 AM, Andrey Semashev via Boost < boost@lists.boost.org> wrote:
On 07/11/18 02:10, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I would like to merge to Boost.Atomic master this commit:
https://github.com/boostorg/atomic/commit/6e14ca24dab50ad4c1 fa8c27c7dd6f1cb791b534
It fixes compilation with clang. Multiple gcc and clang testers have cycled and AppVeyor CI have passed. Travis CI have passed except for Boost.System errors that I mentioned in a recent post.
Approved. -- Marshall
On Tue, Jul 10, 2018 at 4:10 PM, Marshall Clow via Boost <boost@lists.boost.org> wrote:
<https://github.com/boostorg/boost/wiki/Release-Beta-Merge-Policy>
I have 3 commits I'd like to merge: Use the exchange() idiom in move constructors https://github.com/vinniefalco/beast/commit/8ed039200df744f2b5534b0bbf1ce688... Most members of std::allocate are deprecated in C++17 https://github.com/vinniefalco/beast/commit/e0f4c1d7693158fb69f2012cda5b052e... Remove some unused variables https://github.com/vinniefalco/beast/commit/283c9f26f3d5587c2cadc2c65a2325ff... These are code hygiene changes that resolve warnings, and do not affect run-time behavior. Thanks
On Mon, Jul 23, 2018 at 10:44 AM, Vinnie Falco via Boost < boost@lists.boost.org> wrote:
On Tue, Jul 10, 2018 at 4:10 PM, Marshall Clow via Boost <boost@lists.boost.org> wrote:
<https://github.com/boostorg/boost/wiki/Release-Beta-Merge-Policy>
I have 3 commits I'd like to merge:
Use the exchange() idiom in move constructors https://github.com/vinniefalco/beast/commit/8ed039200df744f2b5534b0bbf1ce6 8816a68521
Most members of std::allocate are deprecated in C++17 https://github.com/vinniefalco/beast/commit/e0f4c1d7693158fb69f2012cda5b05 2e68a7fadf
Remove some unused variables https://github.com/vinniefalco/beast/commit/283c9f26f3d5587c2cadc2c65a2325 ff66f8fac3
These are code hygiene changes that resolve warnings, and do not affect run-time behavior.
Approved.
-- Marshall
On Tue, Jul 10, 2018 at 4:10 PM, Marshall Clow via Boost
...
I'd like to merge to master this fix for an example, it resolves incorrect behavior: <https://github.com/vinniefalco/beast/commit/ba4bdfed71659dc12d81d9b71f2870efea7b523c> Thanks
On 11.07.18 01:10, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
-- Marshall
Hi, I took the liberty to merge https://github.com/boostorg/test/commit/cf0acbc38e92f76627ca80e73b63c9fefd66... that contains only documentation changes into Boost.Test. Sorry for not asking permission first, I am not sure I will be able to access the Internet in the next hours :) Best, Raffi
Marshall Clow via Boost <boost@lists.boost.org> writes:
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>
The master branch will close for the 1.68.0 release on August 1st.
Can you merge https://github.com/boostorg/gil/pull/119 ? Impact if declined: GIL/IO cannot be used on DragonFly, FreeBSD, OpenBSD. Affected downstream: https://github.com/freeorion/freeorion/pull/2221#issuecomment-406627682 Workaround if possible: FreeBSD can mimic -traditional via -U__STDC__, DragonFly and OpenBSD would have to create stub <malloc.h> and adjust CPPFLAGS. Tests results: Flast-FreeBSD11 is green on https://www.boost.org/development/tests/develop/developer/gil-io.html but I couldn't figure out if anything else has changed. Risk: Low, can only break build. C++ forbids implicit function declaration.
On 2018-07-29 04:13 PM, Jan Beich wrote:
Marshall Clow via Boost <boost@lists.boost.org> writes:
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>
The master branch will close for the 1.68.0 release on August 1st. Can you merge https://github.com/boostorg/gil/pull/119 ?
It's already on the `develop` branch. It includes a few other last-minute fixes, and so I intend to merge it to `master` before the deadline. Stefan -- ...ich hab' noch einen Koffer in Berlin...
Marshall Clow Via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I'd like to merge the following fix for unused variable warnings: https://github.com/boostorg/geometry/commit/e2ad044720bcbe71e6423c7cea382959... Adam
On Sun, Jul 29, 2018 at 3:00 PM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Marshall Clow Via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I'd like to merge the following fix for unused variable warnings: https://github.com/boostorg/geometry/commit/e2ad044720bcbe71 e6423c7cea3829592cef3c10
The changes look fine to me. Have the test bots cycled? If they have, then go ahead. If they have not, then wait until they have, and (assuming no problems) go ahead. -- Marshall
Marshall Clow Via Boost wrote:
The changes look fine to me. Have the test bots cycled? If they have, then go ahead. If they have not, then wait until they have, and (assuming no problems) go ahead.
Is it still possible to push this MSVC workaround: https://github.com/boostorg/geometry/commit/319ee31d6acf30bec24b03cea3b19f26... Adam
On Wed, Aug 1, 2018 at 5:16 AM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Marshall Clow Via Boost wrote:
The changes look fine to me. Have the test bots cycled? If they have, then go ahead. If they have not, then wait until they have, and (assuming no problems) go ahead.
Is it still possible to push this MSVC workaround: https://github.com/boostorg/geometry/commit/319ee31d6acf30be c24b03cea3b19f26ab940aa1
Same questions as above. That commit is two hours old - I doubt the test bots have cycled yet. The deadline is tonight (PDT). -- Marshall
Marshall Clow Via Boost wrote:
On Wed, Aug 1, 2018 at 5:16 AM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Marshall Clow Via Boost wrote:
The changes look fine to me. Have the test bots cycled? If they have, then go ahead. If they have not, then wait until they have, and (assuming no problems) go ahead.
Is it still possible to push this MSVC workaround: https://github.com/boostorg/geometry/commit/319ee31d6acf30be c24b03cea3b19f26ab940aa1
Same questions as above. That commit is two hours old - I doubt the test bots have cycled yet. The deadline is tonight (PDT).
If you're talking about Travis it has: https://travis-ci.org/boostorg/boost/builds/410777938 At CircleCI there is some failure but AFAIU it has nothing to do with Geometry and the next one passes: https://circleci.com/gh/boostorg/boost Regression for Geometry at CircleCI is ok too: https://circleci.com/workflow-run/a8d3be62-7e27-404a-8951-e0697542fb64 Adam
On Wed, Aug 1, 2018 at 7:20 AM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Marshall Clow Via Boost wrote:
On Wed, Aug 1, 2018 at 5:16 AM, Adam Wulkiewicz via Boost < boost@lists.boost.org> wrote:
Marshall Clow Via Boost wrote:
The changes look fine to me.
Have the test bots cycled? If they have, then go ahead. If they have not, then wait until they have, and (assuming no problems) go ahead.
Is it still possible to push this MSVC workaround: https://github.com/boostorg/geometry/commit/319ee31d6acf30be c24b03cea3b19f26ab940aa1
Same questions as above.
That commit is two hours old - I doubt the test bots have cycled yet. The deadline is tonight (PDT).
If you're talking about Travis it has: https://travis-ci.org/boostorg/boost/builds/410777938 At CircleCI there is some failure but AFAIU it has nothing to do with Geometry and the next one passes: https://circleci.com/gh/boostorg/boost Regression for Geometry at CircleCI is ok too: https://circleci.com/workflow-run/a8d3be62-7e27-404a-8951-e0697542fb64
Then go ahead and merge. -- Marshall
On Tue, Jul 10, 2018 at 4:10 PM, Marshall Clow via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges
Users seem to love to wait until right before a release to submit defects to Beast, and this release is no exception. This is a breaking bug whose fix needs to get into the beta. I have added a unit test which fails before and passes after the proposed resolution, here are the commits: Fix parse_dec algorithm <https://github.com/vinniefalco/beast/commit/802390886d401003925f1421da8ca03667b4ebd1> Add parse_dec tests <https://github.com/vinniefalco/beast/commit/6d1bd38012c09ad17d36ad849b25493322eed0ef> I'd like to merge this to master. The consequence of not merging it, is that HTTP messages with large values for Content-Length may be parsed incorrectly. Thanks
On Sun, Jul 29, 2018 at 5:08 PM, Vinnie Falco via Boost < boost@lists.boost.org> wrote:
On Tue, Jul 10, 2018 at 4:10 PM, Marshall Clow via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges
Users seem to love to wait until right before a release to submit defects to Beast, and this release is no exception.
This is a breaking bug whose fix needs to get into the beta. I have added a unit test which fails before and passes after the proposed resolution, here are the commits:
Fix parse_dec algorithm <https://github.com/vinniefalco/beast/commit/ 802390886d401003925f1421da8ca03667b4ebd1>
Add parse_dec tests <https://github.com/vinniefalco/beast/commit/ 6d1bd38012c09ad17d36ad849b25493322eed0ef>
I'd like to merge this to master. The consequence of not merging it, is that HTTP messages with large values for Content-Length may be parsed incorrectly.
Vinnie -- Once the bots have cycled, and the tests are passing, go ahead. -- Marshall
On 07/11/18 02:10, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I would like to merge this commit to Boost.Atomic master: https://github.com/boostorg/atomic/commit/19eecf893c665410de63ab6ebb8549f405... It fixes "unused argument" warnings with clang.
On Mon, Jul 30, 2018 at 2:18 AM, Andrey Semashev via Boost < boost@lists.boost.org> wrote:
On 07/11/18 02:10, Marshall Clow via Boost wrote:
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>
The master branch will close for the 1.68.0 release on August 1st.
I would like to merge this commit to Boost.Atomic master:
https://github.com/boostorg/atomic/commit/19eecf893c665410de 63ab6ebb8549f405703e80
It fixes "unused argument" warnings with clang.
Approved. -- Marshall
participants (11)
-
Adam Wulkiewicz -
Andrey Semashev -
Andrzej Krzemienski -
Deniz Bahadir -
Edward Diener -
Jan Beich -
Kohei Takahashi -
Marshall Clow -
Raffi Enficiaud -
Stefan Seefeld -
Vinnie Falco