summaryrefslogtreecommitdiff
path: root/docs/source/markdown/podman-machine-init.1.md
diff options
context:
space:
mode:
authorEd Santiago <santiago@redhat.com>2022-03-23 12:29:08 -0600
committerEd Santiago <santiago@redhat.com>2022-03-23 13:49:42 -0600
commit9b0c8d23bddd0fccd6a1faa3fa7f5b7e0373f541 (patch)
tree37dad6631948e2cfa28165a423c6bf22f9ab4d1e /docs/source/markdown/podman-machine-init.1.md
parent73713062806aa4c2db25dc62e2fff47406085dc8 (diff)
downloadpodman-9b0c8d23bddd0fccd6a1faa3fa7f5b7e0373f541.tar.gz
podman-9b0c8d23bddd0fccd6a1faa3fa7f5b7e0373f541.tar.bz2
podman-9b0c8d23bddd0fccd6a1faa3fa7f5b7e0373f541.zip
man pages: sort flags, and keep them that way
Command flags (OPTIONS) in man pages have to date been in haphazard order. Sometimes that order is sensible, e.g., most-important options first, but more often they're just in arbitrary places. This makes life hard for users. Here, I update the man-page-check Makefile script so it checks and enforces alphabetical order in OPTIONS sections. Then -- the hard part -- update all existing man pages to conform to this requirement. Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to 'docs/source/markdown/podman-machine-init.1.md')
-rw-r--r--docs/source/markdown/podman-machine-init.1.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/source/markdown/podman-machine-init.1.md b/docs/source/markdown/podman-machine-init.1.md
index 36db5b1cd..ac258eaae 100644
--- a/docs/source/markdown/podman-machine-init.1.md
+++ b/docs/source/markdown/podman-machine-init.1.md
@@ -32,6 +32,10 @@ Number of CPUs.
Size of the disk for the guest VM in GB.
+#### **--help**
+
+Print usage statement.
+
#### **--ignition-path**
Fully qualified path of the ignition file.
@@ -83,10 +87,6 @@ so mounts must be created under the /mnt directory.
Driver to use for mounting volumes from the host, such as `virtfs`.
-#### **--help**
-
-Print usage statement.
-
## EXAMPLES
```