Update our fork from upstream #2
Conversation
|
FYI - this is going to be big enough that's its going to be hard to review. So probably just going to approve when the time comes. |
@BenjamenMeyer understood. There's really only a few lines of changes that I make on top of each new delta from upstream. And we may not need to keep maintaining this repository anyway; in my latest branch, I've found a way to avoid using this repo altogether. Will keep you updated. |
|
Might be wise to setup a GitHub action to do rebases and submit PRs, dependabot style |
|
@BenjamenMeyer can we close this PR, and archive our fork of the repo? We don't need it with the latest 0.9.x code. Also, can you maybe cut a new 0.9 alpha or beta release, if you haven't already? I'm a bit concerned that alpha 4 may be pulling the outdated code from our fork of this repo. Which wouldn't be good, because that might pull in the compromised Thanks! |
…997) Co-authored-by: Billy O'Neal (VC AIR) <[email protected]>
…41366) Co-authored-by: Kai Pastor <[email protected]>
Co-authored-by: Andrew Mee <[email protected]>
Co-authored-by: Monica <[email protected]>
Co-authored-by: Mengna-Li <[email protected]>
In addition to a new pair of triplets ({x86,x64}-windows-win10) this
requires patching Boost.Log to add an import library.
See boostorg/log#177 for details.
No description provided.