From: Richard Jones <rjones@trick.home.annexia.org>
Date: Mon, 5 Oct 2009 16:58:53 +0000 (+0100)
Subject: Update manpage with --version option.
X-Git-Tag: 1.0.5~41
X-Git-Url: http://git.annexia.org/?p=virt-top.git;a=commitdiff_plain;h=53d7f8573349e27a3decad8cfbee7448554f17d1

Update manpage with --version option.
---

diff --git a/virt-top/virt-top.1 b/virt-top/virt-top.1
index 1406317..0a49ce1 100755
--- a/virt-top/virt-top.1
+++ b/virt-top/virt-top.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.07)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -132,7 +132,7 @@
 .\" ========================================================================
 .\"
 .IX Title "VIRT-TOP 1"
-.TH VIRT-TOP 1 "2008-04-17" "ocaml-libvirt-0.4.1.0" "Virtualization Support"
+.TH VIRT-TOP 1 "2009-10-05" "virt-top-1.0.4" "Virtualization Support"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
@@ -315,6 +315,9 @@ for details).
 .IP "\fB\-\-help\fR" 4
 .IX Item "--help"
 Display usage summary.
+.IP "\fB\-\-version\fR" 4
+.IX Item "--version"
+Display version number and exit.
 .SH "KEYS"
 .IX Header "KEYS"
 Note that keys are case sensitive.  For example use upper-case \fIP\fR
@@ -495,9 +498,14 @@ and keep \fIvirt\-top.log\fR.  It contains error messages which you
 should submit with your bug report.
 .IP "3. Get version of virt-top and version of libvirt." 4
 .IX Item "3. Get version of virt-top and version of libvirt."
-In virt-top, press the \fIh\fR (help) key, and write down the version of
-virt-top and the version of libvirt.  They are shown in the first
-line.
+Use:
+.Sp
+.Vb 1
+\& virt\-top \-\-version
+.Ve
+.Sp
+If you can get the precise version of libvirt you are using
+then that too is helpful.
 .IP "4. Submit a bug report." 4
 .IX Item "4. Submit a bug report."
 Go to <https://bugzilla.redhat.com/> and enter a new bug.
diff --git a/virt-top/virt-top.pod b/virt-top/virt-top.pod
index 4b57811..283185d 100755
--- a/virt-top/virt-top.pod
+++ b/virt-top/virt-top.pod
@@ -196,6 +196,10 @@ for details).
 
 Display usage summary.
 
+=item B<--version>
+
+Display version number and exit.
+
 =back
 
 =head1 KEYS
@@ -425,9 +429,12 @@ should submit with your bug report.
 
 =item 3. Get version of virt-top and version of libvirt.
 
-In virt-top, press the I<h> (help) key, and write down the version of
-virt-top and the version of libvirt.  They are shown in the first
-line.
+Use:
+
+ virt-top --version
+
+If you can get the precise version of libvirt you are using
+then that too is helpful.
 
 =item 4. Submit a bug report.
 
diff --git a/virt-top/virt-top.txt b/virt-top/virt-top.txt
index d222451..624b620 100644
--- a/virt-top/virt-top.txt
+++ b/virt-top/virt-top.txt
@@ -152,6 +152,9 @@ OPTIONS
     --help
         Display usage summary.
 
+    --version
+        Display version number and exit.
+
 KEYS
     Note that keys are case sensitive. For example use upper-case *P* (shift
     P) to sort by %CPU. *^* before a key means a Ctrl key, so *^L* is Ctrl
@@ -310,9 +313,12 @@ REPORTING BUGS
         submit with your bug report.
 
     3. Get version of virt-top and version of libvirt.
-        In virt-top, press the *h* (help) key, and write down the version of
-        virt-top and the version of libvirt. They are shown in the first
-        line.
+        Use:
+
+         virt-top --version
+
+        If you can get the precise version of libvirt you are using then
+        that too is helpful.
 
     4. Submit a bug report.
         Go to <https://bugzilla.redhat.com/> and enter a new bug. Please