-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fix output on short version flag #5348
Conversation
Keep -V behavior same with v2.x Signed-off-by: lucklove <gnu.crazier@gmail.com>
b424913
to
0dd3b16
Compare
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.
LGTM
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.
LGTM
Actually just removing the version(...)
is the same :)
/run-all-tests |
This reverts commit 3c49ba8.
/run-cherry-picker |
cherry pick to release-3.0 failed |
cherry pick to release-3.1 failed |
Signed-off-by: lucklove <gnu.crazier@gmail.com>
Signed-off-by: lucklove <gnu.crazier@gmail.com> Conflicts: src/bin/tikv-server.rs
Signed-off-by: lucklove <gnu.crazier@gmail.com>
Keep -V behavior same with v2.x
Signed-off-by: lucklove gnu.crazier@gmail.com
What have you changed?
The -V output format of tikv-server and tikv-ctl.
The output of -V in v2.x is something like:
However, in v3.x, it's something like:
And in the newest master, it's:
We should keep the output format same with v2.x, because the tidb and pd's output format is that. I think they should have a unified behavior.
What is the type of the changes?
How is the PR tested?
manual test
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect
tidb-ansible
?No
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Any examples? (optional)