On Fri, 28 Mar 2025 at 10:07, Anders Axelsson via Boost <boost@lists.boost.org> wrote:

Hi,

I stumbled upon a problem found in the 1.87.0 release (and also 1.88 beta1) The issue seems to have been resolved on the develop branch in the actual submodule repo quite some time ago by another developer, but it is yet not included in the top/super project.

The ticket: https://github.com/boostorg/context/issues/297

I also reported another issue for which the same thing has happened: https://lists.boost.org/Archives/boost/2025/03/259232.php

I am very new to the community, so I don't really know what is the typical way of working here. it would be sad if we miss to include an important build issue in the next release just because of some administrative issues, so I am happy to help but like I said, I am not familiar with how I can do that.

Any ideas?

I think that the Boost.Context author is the one that needs to perform the merge. If they are reading this, would it be possible to get the merge done before the release? Thanks, Ruben,

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

missing commits should be pushed Am 27.03.25 um 18:05 schrieb Anders Axelsson via Boost:

Hi,

I stumbled upon a problem found in the 1.87.0 release (and also 1.88 beta1) The issue seems to have been resolved on the develop branch in the actual submodule repo quite some time ago by another developer, but it is yet not included in the top/super project.

The ticket: https://github.com/boostorg/context/issues/297

I am very new to the community, so I don't really know what is the typical way of working here. it would be sad if we miss to include an important build issue in the next release just because of some administrative issues, so I am happy to help but like I said, I am not familiar with how I can do that.

Any ideas?

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost