From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Cc: "Anibal Monsalve Salazar" <anibal@debian.org>,
"Santiago Ruano Rincón" <santiago@debian.org>,
"Anthony Fok" <foka@debian.org>, "Mark Wielaard" <mark@klomp.org>
Subject: [PATCH 2/3] Mention the --help command line option in the documentation.
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190721205419.2904-3-mark@klomp.org> (raw)
In-Reply-To: <20190721205419.2904-1-mark@klomp.org>
Bug-Debian: https://bugs.debian.org/517257
---
bzip2.1 | 12 ++++++++++++
manual.xml | 13 +++++++++++++
2 files changed, 25 insertions(+)
diff --git a/bzip2.1 b/bzip2.1
index 174b15f..11d97bb 100644
--- a/bzip2.1
+++ b/bzip2.1
@@ -13,6 +13,9 @@ bzip2recover \- recovers data from damaged bzip2 files
[
.I "filenames \&..."
]
+.br
+.B bzip2
+.RB [ " \-h|\-\-help " ]
.ll -8
.br
.B bunzip2
@@ -21,12 +24,18 @@ bzip2recover \- recovers data from damaged bzip2 files
.I "filenames \&..."
]
.br
+.B bunzip2
+.RB [ " \-h|\-\-help " ]
+.br
.B bzcat
.RB [ " \-s " ]
[
.I "filenames \&..."
]
.br
+.B bzcat
+.RB [ " \-h|\-\-help " ]
+.br
.B bzip2recover
.I "filename"
@@ -238,6 +247,9 @@ Verbose mode -- show the compression ratio for each file processed.
Further \-v's increase the verbosity level, spewing out lots of
information which is primarily of interest for diagnostic purposes.
.TP
+.B \-h \-\-help
+Print a help message and exit.
+.TP
.B \-L --license -V --version
Display the software version, license terms and conditions.
.TP
diff --git a/manual.xml b/manual.xml
index ea9fca2..7c9e4ec 100644
--- a/manual.xml
+++ b/manual.xml
@@ -160,12 +160,21 @@ else.</para>
<listitem><para><computeroutput>bzip2</computeroutput> [
-cdfkqstvzVL123456789 ] [ filenames ... ]</para></listitem>
+ <listitem><para><computeroutput>bzip2</computeroutput> [
+ -h | --help ]</para></listitem>
+
<listitem><para><computeroutput>bunzip2</computeroutput> [
-fkvsVL ] [ filenames ... ]</para></listitem>
+ <listitem><para><computeroutput>bunzip2</computeroutput> [
+ -h | --help ]</para></listitem>
+
<listitem><para><computeroutput>bzcat</computeroutput> [ -s ] [
filenames ... ]</para></listitem>
+ <listitem><para><computeroutput>bzcat</computeroutput> [
+ -h | --help ]</para></listitem>
+
<listitem><para><computeroutput>bzip2recover</computeroutput>
filename</para></listitem>
@@ -397,6 +406,10 @@ consistency error (eg, bug) which caused
will not be suppressed.</para></listitem>
</varlistentry>
+ <varlistentry><term><computeroutput>-h --help</computeroutput></term>
+ <listitem><para>Print a help message and exit.</para></listitem>
+ </varlistentry>
+
<varlistentry>
<term><computeroutput>-v --verbose</computeroutput></term>
<listitem><para>Verbose mode -- show the compression ratio for
--
2.20.1
next prev parent reply other threads:[~2019-07-21 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Some bzip2 manual page patches from Debian Mark Wielaard
2019-01-01 0:00 ` [PATCH 3/3] Add generation of bzip2.txt and bzip2.1.preformatted to Makefile Mark Wielaard
2019-01-01 0:00 ` [PATCH 1/3] bzip2.1: remove blank spaces in man page and drop the .PU macro Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard [this message]
2019-01-01 0:00 ` Some bzip2 manual page patches from Debian Santiago Ruano Rincón
2019-01-01 0:00 ` Mark Wielaard
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=20190721205419.2904-3-mark@klomp.org \
--to=mark@klomp.org \
--cc=anibal@debian.org \
--cc=bzip2-devel@sourceware.org \
--cc=foka@debian.org \
--cc=santiago@debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).