Skip to content
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

Update E0057 error message to new format #35395

Closed

Conversation

paulfanelli
Copy link
Contributor

Fixes #35214 as part of #35233.

r? @jonathandturner

@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jonathandturner (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.

@sophiajt
Copy link
Contributor

sophiajt commented Aug 5, 2016

Looks good!

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Aug 5, 2016

📌 Commit edca8ec has been approved by jonathandturner

@bors
Copy link
Contributor

bors commented Aug 5, 2016

☔ The latest upstream changes (presumably #35365) made this pull request unmergeable. Please resolve the merge conflicts.

bors added a commit that referenced this pull request Aug 6, 2016
bors added a commit that referenced this pull request Aug 6, 2016
bors added a commit that referenced this pull request Aug 6, 2016
Rollup of 9 pull requests

- Successful merges: #35362, #35393, #35394, #35402, #35410, #35411, #35413, #35419, #35421
- Failed merges: #35395, #35415
bors added a commit that referenced this pull request Aug 7, 2016
bors added a commit that referenced this pull request Aug 7, 2016
Rollup of 6 pull requests

- Successful merges: #35396, #35402, #35446, #35466, #35470, #35475
- Failed merges: #35395, #35415
@bors
Copy link
Contributor

bors commented Aug 8, 2016

🔒 Merge conflict

bors added a commit that referenced this pull request Aug 10, 2016
bors added a commit that referenced this pull request Aug 11, 2016
bors added a commit that referenced this pull request Aug 22, 2016
bors added a commit that referenced this pull request Aug 23, 2016
Rollup of 6 pull requests

- Successful merges: #35910, #35912, #35913, #35936, #35939, #35949
- Failed merges: #35395
@sophiajt
Copy link
Contributor

@paulfanelli - can you update this to fix the merge conflict? With that, I think we're good to go.

@paulfanelli
Copy link
Contributor Author

Will do...I'll take a look at.

bors added a commit that referenced this pull request Aug 25, 2016
Rollup of 4 pull requests

- Successful merges: #35876, #35920, #35948, #35961
- Failed merges: #35395
@paulfanelli
Copy link
Contributor Author

Looks like the reason there was a conflict, is that someone else had also fixed it. To fix the conflict, I updated my fork with the latest rust code and rebased my branch where i did the work (update-e0057-error-msg) onto the lastest rust code. I re-complied and tested it. I then pushed the updated code back to the update-e0057-error-msg branch of my fork. I think this pull request now is good to go. (?)

@sophiajt
Copy link
Contributor

@paulfanelli - if I'm reading this right, did someone fix this issue already? If so, I can close this and you can pick another one from the list (if you like): #35233

@paulfanelli
Copy link
Contributor Author

Yep, someone fixed it, just a bit differently. Ok, go ahead and close this and I'll take #35233 , if still available.

@paulfanelli
Copy link
Contributor Author

Oops, didn't realize that #35233 is the catch-all issue; can't take them all, lol. I'll pick something from the list.

@paulfanelli
Copy link
Contributor Author

Hey, just a heads up, I never did any bonus work on this one. Not sure if whoever fixed it, did either.

@bors
Copy link
Contributor

bors commented Sep 6, 2016

☔ The latest upstream changes (presumably #36274) made this pull request unmergeable. Please resolve the merge conflicts.

@bstrie
Copy link
Contributor

bstrie commented Sep 28, 2016

I believe this is now being addressed by #36222 , so I'll close this (feel free to reopen if I'm wrong). Thanks for the effort in any case! :)

@bstrie bstrie closed this Sep 28, 2016
@sophiajt sophiajt reopened this Sep 28, 2016
@sophiajt
Copy link
Contributor

@bstrie - neither PR has landed, yet. Though given that both haven't moved in over two weeks, perhaps we should close both?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants