-
Notifications
You must be signed in to change notification settings - Fork 727
Change long option #2668
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
Change long option #2668
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.
Hey @sharder996, thanks!
Looks good, hiding the going-to-be-deprecated option seems the best choice to me.
One detail, though: I think that specifying --mem
and --memory
toghether must make Multipass to fail.
If both options are used together, then |
Codecov Report
@@ Coverage Diff @@
## main #2668 +/- ##
==========================================
+ Coverage 86.46% 86.48% +0.01%
==========================================
Files 217 217
Lines 10819 10833 +14
==========================================
+ Hits 9355 9369 +14
Misses 1464 1464
Help us with your feedback. Take ten seconds to tell us how you rate us. |
@sharder996 it seems you answered before I update my question. I didn't read that My point is that, in case the user knows that there is a |
I think if both Also, to take this one step further, I think if |
I like Chris' idea as it gives the user some head ups that the option will be having potentially breaking changes in the future rather than a silent change that still works. |
Hey @sharder996. Thanks, it's much better now! A tiny bit of coverage remaining and we're done. Can you please add coverage to the error messages? |
Excellent, thanks @sharder996! A final detail: can you please change "in favor" to "in favour", so we use UK English in the output? |
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.
Excellent, thanks!
bors r+
2668: Change long option r=luis4a0 a=sharder996 This PR changes the long option for memory allocation of the `launch` command from `--mem` to `--memory`. `--mem` is still supported for backwards compatibility, but will not be displayed in the help text. If both options are used, `--memory` will take precedence. Fixes #2490 for original change request. Co-authored-by: sharder996 <[email protected]> Co-authored-by: ScottH <[email protected]>
Timed out. |
bors r+ |
2667: Linux qemu uefi r=luis4a0 a=andrei-toterman Make QEMU boot using UEFI on Linux fix #1477 2668: Change long option r=sharder996 a=sharder996 This PR changes the long option for memory allocation of the `launch` command from `--mem` to `--memory`. `--mem` is still supported for backwards compatibility, but will not be displayed in the help text. If both options are used, `--memory` will take precedence. Fixes #2490 for original change request. Co-authored-by: Andrei Toterman <[email protected]> Co-authored-by: sharder996 <[email protected]> Co-authored-by: ScottH <[email protected]>
Build failed (retrying...): |
2668: Change long option r=sharder996 a=sharder996 This PR changes the long option for memory allocation of the `launch` command from `--mem` to `--memory`. `--mem` is still supported for backwards compatibility, but will not be displayed in the help text. If both options are used, `--memory` will take precedence. Fixes #2490 for original change request. Co-authored-by: sharder996 <[email protected]> Co-authored-by: ScottH <[email protected]>
Build failed: |
bors retry |
2668: Change long option r=sharder996 a=sharder996 This PR changes the long option for memory allocation of the `launch` command from `--mem` to `--memory`. `--mem` is still supported for backwards compatibility, but will not be displayed in the help text. If both options are used, `--memory` will take precedence. Fixes #2490 for original change request. Co-authored-by: sharder996 <[email protected]> Co-authored-by: ScottH <[email protected]>
Build failed: |
bors retry |
2668: Change long option r=sharder996 a=sharder996 This PR changes the long option for memory allocation of the `launch` command from `--mem` to `--memory`. `--mem` is still supported for backwards compatibility, but will not be displayed in the help text. If both options are used, `--memory` will take precedence. Fixes #2490 for original change request. Co-authored-by: sharder996 <[email protected]> Co-authored-by: ScottH <[email protected]>
Build failed: |
bors retry |
2668: Change long option r=sharder996 a=sharder996 This PR changes the long option for memory allocation of the `launch` command from `--mem` to `--memory`. `--mem` is still supported for backwards compatibility, but will not be displayed in the help text. If both options are used, `--memory` will take precedence. Fixes #2490 for original change request. Co-authored-by: sharder996 <[email protected]> Co-authored-by: ScottH <[email protected]>
Build failed: |
Weird, as usual bors retry |
2668: Change long option r=sharder996 a=sharder996 This PR changes the long option for memory allocation of the `launch` command from `--mem` to `--memory`. `--mem` is still supported for backwards compatibility, but will not be displayed in the help text. If both options are used, `--memory` will take precedence. Fixes #2490 for original change request. Co-authored-by: sharder996 <[email protected]> Co-authored-by: ScottH <[email protected]>
Build failed: |
We'll try this one more time since the other branch was out of sync... bors retry |
Build failed: |
This PR changes the long option for memory allocation of the
launch
command from--mem
to--memory
.--mem
is still supported for backwards compatibility, but will not be displayed in the help text. If both options are used,--memory
will take precedence.Fixes #2490 for original change request.