Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Martin Steigerwald <ms@teamix.de>
To: fio@vger.kernel.org
Subject: [PATCH] Escape minus signs in manpage to fix lintian warning
Date: Wed, 5 Oct 2011 11:46:47 +0200	[thread overview]
Message-ID: <201110051146.47562.ms@teamix.de> (raw)

Hi Jens!

I have patch to fix a recently introduced lintian warning. It is my first
try with "git format-patch origin" and KMail without line wrappings.

Please tell me, whether its okay.

I will include the patch in my debian package until I package a version
where you merged it.


From 0d572b5e317ec8c93d8594c40c05c2464fcef59f Mon Sep 17 00:00:00 2001
From: Martin Steigerwald <ms@teamix.de>
Date: Wed, 5 Oct 2011 11:41:54 +0200
Subject: [PATCH] Escape minus signs in manpage to fix lintian warning:

I: fio: hyphen-used-as-minus-sign usr/share/man/man1/fio.1.gz:934

see:
http://lintian.debian.org/tags/hyphen-used-as-minus-sign.html
---
 fio.1 |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fio.1 b/fio.1
index dc10b40..513caa9 100644
--- a/fio.1
+++ b/fio.1
@@ -931,7 +931,7 @@ Enable the reporting of percentiles of completion latencies.
 Overwrite the default list of percentiles for completion
 latencies. Each number is a floating number in the range (0,100], and
 the maximum length of the list is 20. Use ':' to separate the
-numbers. For example, --percentile_list=99.5:99.9 will cause fio to
+numbers. For example, \-\-percentile_list=99.5:99.9 will cause fio to
 report the values of completion latency below which 99.5% and 99.9% of
 the observed latencies fell, respectively.
 .SH OUTPUT
-- 
1.7.6.3

Thanks,
-- 
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90

             reply	other threads:[~2011-10-05  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05  9:46 Martin Steigerwald [this message]
2011-10-05 12:09 ` [PATCH] Escape minus signs in manpage to fix lintian warning Jens Axboe

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=201110051146.47562.ms@teamix.de \
    --to=ms@teamix.de \
    --cc=fio@vger.kernel.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