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
run-checker: Check enabling and disabling trace #37
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why both? For all other options, only the non-default is specified.
What is the default behaviour of trace? |
It’s currently changing from enabled to disabled, see #8474. |
It's precisely because we're currently in a state of fluctuation that I made it both. (side note: when linking to pull requests in a different repo, you have to be a little more verbose: openssl/openssl#8474) |
Thanks, I know. But I was doing it on my mobile (once again), so I was too lazy :P |
Since openssl/openssl#8474 has been merged meanwhile, I'd prefer having only the non-default now. |
Sure |
Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> (Merged from #37)
Merged. 31b2767 run-checker: Check enabling and disabling trace |
No description provided.