Uh oh!
There was an error while loading. Please reload this page.
errors: Reorder component-unavailable message parts - #1769
Conversation
a60c989 to
ecd8b59Compare
"If you require" (capitalized)?
"for example:" (colon)? Or is it not about the command line, but about URL to look for build status? Then there should be some other introductory sentence before the command line sample, such as |
kinnison
commented
Apr 16, 2019
Fair, I'll get that message updated later. Is this the only problem you have with the result? |
Probably yes, although I'd also specified explicitly that it would not be the The system (tracking nightly which points to some date, plus explicit dated nightlies) is in general a bit confusing, so longer help messages won't hurt. |
The ordering of some of the parts of the component-unavailable error message was unfortunate, resulting in confusion. This reorders those so that errors are slightly clearer. In addition we reword the explanatory text slightly to improve clarity further Fixes: rust-lang#1768 Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
ecd8b59 to
928e768Comparekinnison
commented
Apr 16, 2019
Explanatory message updated to: |
Looks OK. If #1628 is implemented some way (e.g. |
kinnison
commented
Apr 16, 2019
Thanks @vi |
The ordering of some of the parts of the component-unavailable
error message was unfortunate, resulting in confusion. This
reorders those so that errors are slightly clearer.
Fixes: #1768
As an example, the old message form would be:
The new form is:
/cc @vi