Userdocs

I don't think there is any will or intention to update RC_1_2 and whatever time is given will be to RC_2_0. So I guess RC_1_2 will be stuck using 1.86.0.

I'm under the impression that there is no desire to update RC_1_2 any more let alone release another version. We don't see much of arvidn at this time either. Seems...

I'm not sure I see the point of a `RC_1_3` branch just for a boost update. Would it get any feature updates, is it essentially unsupported and will `RC_2_x` be...

The Savannah git is regularly unreachable and the https://ftpmirror.gnu.org/gnu also goes offline periodically. I don't understand what this achieves because as far as I understand it, there is no public...

I think that makes sense. Only enable it if there is a problem, which solve the immediate problem of the host being so unreliable. The only option otherwise is some...

Reference this related commit - drop config.sub replacement https://github.com/richfelker/musl-cross-make/commit/f5a188a976d6b451061a49995a94e95831178c66

what i see with claude.ai ``` ● Now I can see the issue clearly. Both commits are dealing with Boost library version compatibility - specifically migrating from an older version...

@glassez i don't see why not but it would require getting past this boost issue right? as you see from my last post the are two approaches here, only support...

oh ok, but still RC_1_3 won't happen if we don't get the boost thing out of the way, @arvidn seems to not have a not of resources to spare here...

ok, hopefully we can get branch RC_1_3 going. Just need arv to chime in. I will try to make a window/osx/linux workflow to test the pr branch .