Conversation
|
Is this still WIP? |
|
|
I think I've meanwhile fixed all reported issues. |
Not anymore. |
|
I've just added three more fixes:
|
…ODE_UNSAFE_FOR_PRODUCTION
|
@DDvO given you are fixing At the moment we have this: Lines 1657 to 1704 in 200ae2e I don't know what would be best: expanding that section or having a new markdown file inside What do you think? |
|
Thanks @romen for reviewing this and your comments:
Very good point!
I'd say it makes most sense to do a quick documentation extension as part of this PR After this one has been merged I'll do a further PR for cleaning up |
|
24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually. |
Reviewed-by: Nicola Tuveri <[email protected]> (Merged from #12175)
…thout proxy Fixes #12156 Reviewed-by: Nicola Tuveri <[email protected]> (Merged from #12175)
Reviewed-by: Nicola Tuveri <[email protected]> (Merged from #12175)
…ODE_UNSAFE_FOR_PRODUCTION Reviewed-by: Nicola Tuveri <[email protected]> (Merged from #12175)
Reviewed-by: Nicola Tuveri <[email protected]> (Merged from #12175)
Reviewed-by: Nicola Tuveri <[email protected]> (Merged from #12175)
… VFP mode Reviewed-by: Nicola Tuveri <[email protected]> (Merged from #12175)
Reviewed-by: Nicola Tuveri <[email protected]> (Merged from #12175)
| $ ./config | ||
| ./config | ||
| Operating system: x86-whatever-minix | ||
| This system (minix) is not supported. See file INSTALL for details. |
There was a problem hiding this comment.
Damnit, I didn't pay enough attention.
A reason for the $ was to clearly mark what is prompted commands and what is command output. It's even explained here (which, interestingly enough, you ignored in all kinds of ways):
Lines 73 to 81 in 922f156
There was a problem hiding this comment.
I find it incredibly irritating that things like this get "slipped in" in PRs that have nothing to do with it.
There was a problem hiding this comment.
Indeed I overlooked that explanation, but I did suspect that the $ was used for that purpose.
Still I don't like it, because in particular if there is a number of shell commands in a row, such as in
$ mkdir /var/tmp/openssl-build
$ cd /var/tmp/openssl-build
$ whatever
you cannot simply copy&paste that series of commands, while with
mkdir /var/tmp/openssl-build
cd /var/tmp/openssl-build
whatever
you can.
And I suppose there are just a few cases where command input and output could be confused.
In such cases we could, e.g., insert a blank line to help understanding this distinction.
There was a problem hiding this comment.
Regardless, if you want to change that, having that "slip in" in a PR that's about something different is not a good way to do it.
There was a problem hiding this comment.
I find it incredibly irritating that things like this get "slipped in" in PRs that have nothing to do with it.
Yeah, I should better have done this in a separate PR for clarity.
It just had come up along with the review of this PR, so for simplicity I added a commit for that here.
There was a problem hiding this comment.
Regardless, if you want to change that, having that "slip in" in a PR that's about something different is not a good way to do it.
Sorry for that.
There was a problem hiding this comment.
I've just checked: in this (merged) PR this is the only case where command input and output got mixed.
Here I suggest simply dropping the line
./config
because it is already mentioned in the sentence above it.
@levitte, are you okay if I do this nit fix along with #12109 or #12232,
or should I also in this case do a separate PR for it?
There was a problem hiding this comment.
And of course we should be consistent about using $ or not,
and if there is consensus to drop it also remove the remark in INSTALL.md on its purpose quoted above.
There was a problem hiding this comment.
BTW, the $ symbols is not commonly used under Windows, where typically a > is printed as prompt.
There was a problem hiding this comment.
I just realized that already today at noon (CEST) a PR restoring the $ has been done: #12257.
Uh oh!
There was an error while loading. Please reload this page.