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
doc/rbd: document cp versus deep cp #41529
Conversation
This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved |
c495166
to
f2e4fe8
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.
There is more to deep copy
than just snapshots, but it is probably the most important aspect and having it mentioned in the help output seems worthwhile.
Sorry, one more thing -- please update the commit title to match the title of the PR (I have tweaked it). |
I found that the difference between "rbd cp" and "rbd deep cp", i.e. what "deep" means in this context, is documented only in the mailing list archive and in the Mimic reelase notes. Let's make the difference explicit in the manpage and in rbd --help. Signed-off-by: Jan "Yenya" Kasprzak <kas@fi.muni.cz>
Done. |
I found that the difference between "rbd cp" and "rbd deep cp",
i.e. what "deep" means in this context, is documented only in
the mailing list archive and in the Mimic reelase notes.
Let's make the difference explicit in the manpage and in rbd --help.
Signed-off-by: Jan "Yenya" Kasprzak kas@fi.muni.cz
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox