|
123
|
On 11/15/20 11:05 AM, Marshall Clow via Boost wrote:
request permission to sync changes in develop into master for two
libraries: serialization and safe_numerics. They've been ready for some
time, I just forgot to do it in time.
Robert Ramey
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
|
In reply to this post by Boost - Dev mailing list
On 15/11/2020 19:05, 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.
boostorg/outcome now has the fix for the exception throw failure on
master branch. I'll watch the regression matrix, see if it now goes all
green.
Niall
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
|
On Sun, Nov 15, 2020 at 7:06 PM Niall Douglas wrote:
>
> On 15/11/2020 19:05, 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.
>
> boostorg/outcome now has the fix for the exception throw failure on
> master branch. I'll watch the regression matrix, see if it now goes all
> green.
Permission for merges to master are required at this point. You should
commit to develop, let he tests cycle, and then request permission to
merge to master.
Glen
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
|
In reply to this post by Boost - Dev mailing list
Robert Ramey wrote:
> request permission to sync changes in develop into master for
> two libraries: serialization and safe_numerics. They've been ready for
> some time, I just forgot to do it in time.
Go ahead.
Glen
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
|
In reply to this post by Boost - Dev mailing list
On Sun, 15 Nov 2020 at 20:06, Marshall Clow via Boost < [hidden email]>
wrote:
> The master branch is is now open for post-beta merges, but only as
> described in the Post-Beta Merge Policy.
>
I have some minor Beast fixes that have been successfully tested on develop.
Seeking permission to merge to master.
--
Richard Hodges
[hidden email]
office: +442032898513
home: +376841522
mobile: +376380212
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
|
On Monday, November 16, 2020, Richard Hodges wrote:
> I have some minor Beast fixes that have been successfully tested on
> develop.
>
> Seeking permission to merge to master.
Go ahead.
Glen
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
|
In reply to this post by Boost - Dev mailing list
On Sun, Nov 15, 2020 at 11:05 AM Marshall Clow via Boost
< [hidden email]> wrote:
> The master branch is is now open for post-beta merges, but only as
> described in the Post-Beta Merge Policy.
I would like to merge this fix for docca (it is a tool used to build
documentation for Beast and JSON):
< https://github.com/boostorg/docca/commit/36187e2c964f000c259cca32b48371fe068e46fe>
it isn't essential, and it could break the doc build. I have merged it
to develop.
Also, Peter has convinced me to revert the is_integral change, as
adding features post-beta is probably not a good idea (and I think the
feature might not be as great as I imagined).
Thanks
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
|
In reply to this post by Boost - Dev mailing list
On 16/11/2020 01:13, Glen Fernandes wrote:
> On Sun, Nov 15, 2020 at 7:06 PM Niall Douglas wrote:
>>
>> On 15/11/2020 19:05, 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.
>>
>> boostorg/outcome now has the fix for the exception throw failure on
>> master branch. I'll watch the regression matrix, see if it now goes all
>> green.
>
> Permission for merges to master are required at this point. You should
> commit to develop, let he tests cycle, and then request permission to
> merge to master.
Looks like someone git reset master branch to undo my fix. Thank you to
whomever did that.
May I have permission to merge the fix for the exception throw failure
to master branch?
Niall
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
|
On Wednesday, November 18, 2020, Niall Douglas via Boost <
[hidden email]> wrote:
> On 16/11/2020 01:13, Glen Fernandes wrote:
> > On Sun, Nov 15, 2020 at 7:06 PM Niall Douglas wrote:
> >>
> >> On 15/11/2020 19:05, 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.
> >>
> >> boostorg/outcome now has the fix for the exception throw failure on
> >> master branch. I'll watch the regression matrix, see if it now goes all
> >> green.
> >
> > Permission for merges to master are required at this point. You should
> > commit to develop, let he tests cycle, and then request permission to
> > merge to master.
>
> Looks like someone git reset master branch to undo my fix. Thank you to
> whomever did that.
>
> May I have permission to merge the fix for the exception throw failure
> to master branch?
>
>
Go ahead.
Glen
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
|
123
|