-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
import boost-1.58 #1528
import boost-1.58 #1528
Conversation
dbe6eb9
to
aab54bf
Compare
aab54bf
to
c69da82
Compare
ping |
This should be for 3.8? We can pull once 3.7 is out, unless there are important 3.7 bugs that will be fixed by this. |
if |
We can create a 3.7 branch any time - we've held off thus far to concentrate attention on locking down 3.7 fixes, with the intention that we would branch when there were changes that needed to be shared in the main repo and were important enough to justify branching. This is probably a good candidate for that branch, especially if you have further development work to do on top of this. |
4c8eb13
to
2103dd1
Compare
fwiw, it would be nice if this could at one point be merged, as it block some further changes (read: bug fixes) of supernova |
@scztt @timblechmann is it defendable to do this for 3.7.0 or 3.7.x? I don't know enough about the consequences to be able to decide this. |
make the 3.7 branch!!!!!!!!!!!!!!!!!!!!!!!!! |
3.7 is made and pushed On Sun, Dec 6, 2015 at 10:29 AM danstowell [email protected] wrote:
|
Don't merge it to 3.7, there is no reason to introduce any risk, there is On Sun, Dec 6, 2015 at 11:31 AM Chris Sattinger [email protected]
|
This compiles fine for me, and SC boots and makes the noises I expect it to make. I suggest merging this into master. (Note: the title of the PR is a bit wrong, since Tim later updated this branch to boost-1.59.) |
and use official boost.endian