From: Zdenek Kabelac <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: main - make: generate
Date: Sun, 10 Jul 2022 23:22:27 +0000 (GMT) [thread overview]
Message-ID: <20220710232227.7178C385737B@sourceware.org> (raw)
Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=c0f8e6675c62332263acdc7c3c2f61eca20bd60f
Commit: c0f8e6675c62332263acdc7c3c2f61eca20bd60f
Parent: 4d2f9a4ff3fbfe4ee0df08478d81ea10f75823de
Author: Zdenek Kabelac <zkabelac@redhat.com>
AuthorDate: Mon Jul 11 01:02:22 2022 +0200
Committer: Zdenek Kabelac <zkabelac@redhat.com>
CommitterDate: Mon Jul 11 01:18:24 2022 +0200
make: generate
---
man/pvdisplay.8_pregen | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/man/pvdisplay.8_pregen b/man/pvdisplay.8_pregen
index 23d41b29b..e7767d0c4 100644
--- a/man/pvdisplay.8_pregen
+++ b/man/pvdisplay.8_pregen
@@ -61,6 +61,8 @@ and more, using a more compact and configurable output format.
.br
[ \fB--readonly\fP ]
.br
+[ \fB--reportformat\fP \fBbasic\fP|\fBjson\fP ]
+.br
[ \fB--separator\fP \fIString\fP ]
.br
[ \fB--shared\fP ]
@@ -320,6 +322,16 @@ device-mapper kernel driver, so this option is unable to report whether
or not LVs are actually in use.
.
.HP
+\fB--reportformat\fP \fBbasic\fP|\fBjson\fP
+.br
+Overrides current output format for reports which is defined globally by
+the report/output_format setting in \fBlvm.conf\fP(5).
+\fBbasic\fP is the original format with columns and rows.
+If there is more than one report per command, each report is prefixed
+with the report name for identification. \fBjson\fP produces report
+output in JSON format. See \fBlvmreport\fP(7) for more information.
+.
+.HP
\fB-S\fP|\fB--select\fP \fIString\fP
.br
Select objects for processing and reporting based on specified criteria.
next reply other threads:[~2022-07-10 23:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 23:22 Zdenek Kabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-23 16:09 main - make: generate Zdenek Kabelac
2023-03-22 12:44 Tony Asleson
2023-03-21 12:39 Marian Csontos
2022-11-10 13:22 Marian Csontos
2022-09-21 12:59 Zdenek Kabelac
2022-08-11 11:06 Peter Rajnoha
2022-05-18 16:15 Marian Csontos
2022-05-03 17:11 Zdenek Kabelac
2022-02-07 19:03 Zdenek Kabelac
2021-10-14 21:37 Zdenek Kabelac
2021-10-07 17:43 David Teigland
2021-09-23 14:52 Zdenek Kabelac
2021-08-09 14:27 Marian Csontos
2021-05-07 15:45 Marian Csontos
2021-04-23 21:06 Zdenek Kabelac
2021-04-19 13:01 Zdenek Kabelac
2021-04-12 9:13 Zdenek Kabelac
2021-04-12 7:55 Zdenek Kabelac
2021-03-19 23:17 Zdenek Kabelac
2021-03-05 12:01 Marian Csontos
2021-03-02 21:58 Zdenek Kabelac
2021-02-17 10:54 Zdenek Kabelac
2021-01-18 13:46 Marian Csontos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220710232227.7178C385737B@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.