Write stderr output from build-scripts next to stdout output#4088
Write stderr output from build-scripts next to stdout output#4088bors merged 2 commits intorust-lang:masterfrom
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (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. |
|
@bors: r+ Thanks |
|
📌 Commit 8fa39fc has been approved by |
Write stderr output from build-scripts next to stdout output Closes #3462. Please let me know if you want to change the file name for the error output. I originally thought that `stdout` and `stderr` would have been nice but I'm worried that changing `output` to `stdout` would cause breakage. So I choose the more conservative route.
|
☀️ Test successful - status-appveyor, status-travis |
Closes #3462.
Please let me know if you want to change the file name for the error output. I originally thought that
stdoutandstderrwould have been nice but I'm worried that changingoutputtostdoutwould cause breakage. So I choose the more conservative route.