-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Stabilize fs::read and fs::write #49422
Conversation
r? @TimNN (rust_highfive has picked a reviewer for you, use r? to override) |
This fails tidy because the the still-unstable |
I like just changing the feature to |
Done. |
@bors r+ |
📌 Commit 0600d0f has been approved by |
Remember to change the version to 1.26.0 if this merges before someone has got time to branch the beta. |
⌛ Testing commit 0600d0f with merge a51aa6a08de689ce61f43d27ecc76448155dc627... |
💔 Test failed - status-appveyor |
One of the appveyor jobs hit the 3 hour limit. Can someone retry it? |
@bors retry
…On Fri 30. Mar 2018 at 00:31, Matt Brubeck ***@***.***> wrote:
One of the appveyor jobs hit the 3 hour limit. Can someone retry it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#49422 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABH6iW96G2JbVDpEEd5KzT_4twyb9WsRks5tjWDRgaJpZM4S9VH6>
.
|
Stabilize fs::read and fs::write As discussed in #46588 (comment)
☀️ Test successful - status-appveyor, status-travis |
Oh, it looks like I misinterpreted one of the commits on the |
As discussed in #46588 (comment)