-
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
Auto #58682
Auto #58682
Conversation
Unfortunately this'll dupe parking_lot until the data_structures crate is published and be updated in rls in conjunction with crossbeam-channel
Update parking_lot to 0.7 Unfortunately this'll dupe parking_lot until the data_structures crate is published and be updated in rls in conjunction with crossbeam-channel
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
Opened by accident I presume? Closing. |
Merge so I can review the code
…On Sat, Feb 23, 2019, 10:58 PM Rust highfive robot ***@***.*** wrote:
Thanks for the pull request, and welcome! The Rust team is excited to
review your changes, and you should hear from @nikomatsakis
<https://github.com/nikomatsakis> (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra
commits. This ensures that the reviewer can see what has changed since they
last reviewed the code. Due to the way GitHub handles out-of-date commits,
this should also make it reasonably obvious what issues have or haven't
been addressed. Large or tricky changes may require several passes of
review and changes.
Please see the contribution instructions
<https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md> for more
information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#58682 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ARn-PIS165ActbbtnYBEf8O-m64aD9djks5vQZ2BgaJpZM4bOIU9>
.
|
The branch just contains #57051, so not sure why you need another PR? |
CI is failing
…On Sat, Feb 23, 2019, 10:58 PM Rust highfive robot ***@***.*** wrote:
Thanks for the pull request, and welcome! The Rust team is excited to
review your changes, and you should hear from @nikomatsakis
<https://github.com/nikomatsakis> (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra
commits. This ensures that the reviewer can see what has changed since they
last reviewed the code. Due to the way GitHub handles out-of-date commits,
this should also make it reasonably obvious what issues have or haven't
been addressed. Large or tricky changes may require several passes of
review and changes.
Please see the contribution instructions
<https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md> for more
information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#58682 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ARn-PIS165ActbbtnYBEf8O-m64aD9djks5vQZ2BgaJpZM4bOIU9>
.
|
Auto