Closed rst0git closed 1 year ago
Patch coverage: 100.00
% and project coverage change: +0.19
:tada:
Comparison is base (
0405c79
) 80.56% compared to head (b52f036
) 80.75%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
23 tests ±0 23 :heavy_check_mark: ±0 0s :stopwatch: ±0s 1 suites ±0 0 :zzz: ±0 1 files ±0 0 :x: ±0
Results for commit b52f0360. ± Comparison against base commit 0405c795.
:recycle: This comment has been updated with latest results.
Wouldn't some of these shorthands conflict with future additions? E.g. -f
for --full-paths
could be mistaken for --fds
.
Wouldn't some of these shorthands conflict with future additions? E.g.
-f
for--full-paths
could be mistaken for--fds
.
Good question. I expect there will be similar conflicts with future additions. Should use -A
and -F
(capitals) for --all
and --full-paths
? Then, -f
(lowercase) could be used as a shorthand for --fds
.
That would work nicely!
I understand the reason for this PR, but I am still a bit undecided. Maybe we should wait a bit longer until we have more features before introducing shorthand options. Once we have more flags, maybe we can see better how to distribute the shorthand flags. Just an idea.
Closing this PR in favour of the changes introduced with https://github.com/checkpoint-restore/checkpointctl/pull/76
This patch enables the following shorthand options: