-
Notifications
You must be signed in to change notification settings - Fork 22
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
Improve man and documentation #56
Comments
Yes. Creating high-quality documentation requires considerable effort. |
Hi. |
@SergeiShtepa It seems to me that you have improved the documentation a lot, to know if it is sufficient we would need to see the opinion of some users. |
OK. Let it stay that way for now. |
Description
Seems to me that actually man of blksnap tool and documentation is "minimal" and for understand how to use it "fast" is need for example to look to tests scripts and in some cases require also looking at the source code to understand better.
I think can be useful to improve man and blksnap help texts to make easier and faster do common blksnap usage. It might also be helpful to do some small howto's of some common usage examples.
Looking for example the man recently added in stable-2.0 an explanation could be made regarding "stretch_snapshot" which I think is quite important. "snapshot_create" and "snapshot_add" they would seem unclear at first glance, they don't take the actual snapshot (done by "snapshot_take") but they "prepare" to do it, maybe they could be called differently but I can't think of a clear name and maybe it's enough to specify better in the man and in the help of the tool, perhaps also specifying in "snapshot_take" that the preparation and addition of storage for the differences is required first.
Unfortunately I'm not good at explaining and also write in English so I think many people could improve/add documentation better and faster. If it won't be done by other contributors, I would eventually try to do it.
Usage tips
The text was updated successfully, but these errors were encountered: