From: Christoph Anton Mitterer <calestyo@scientia.net>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: polishing up mdadm manpages: mdassemble(8), mdmon(8)
Date: Thu, 10 Mar 2011 13:57:29 +0000 [thread overview]
Message-ID: <a5e41cc2828ecc385314e30988be9b7d@imap.dd24.net> (raw)
In-Reply-To: <20110310161827.6df62c7a@notabene.brown>
On Thu, 10 Mar 2011 16:18:27 +1100, NeilBrown <neilb@suse.de> wrote:
> Of course I could create the patch my - it looks like you
> start from the verison in the 3.2 release - correct?
Yes.
> Being consistent is good, but using \fB \fI etc is not.
> Convention (as I understand it) prefers .B .I etc.
Is this convention? I've seen many manpages using it,.. and it seems to be
part of the standard format?
> There are a variety of programs around which convert man pages to
> other formats and I trust the ".B" tags to be handled more reliably.
Well if they don't handle \f* they should be fixed IMHO....
Anyway,.. the reason for me arguing so strong agains .B .I etc. is that it
really makes the (raw) manpage nearly unreadable/unmaintainable IMHO.
Especially polishing up everything is made rather impossible so (IMHO)...
so do you insist on this?.
> Maybe... The ".pid" and ".sock" are file name extensions. If your
change
> were made (which quite possibly improves readability) it might then me
> necessary to say something explicit about extensions.
Well that's up to you then,.. I don't have enough knowledge about the
containers to do that =)
Cheers,
Chris.
prev parent reply other threads:[~2011-03-10 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 3:08 polishing up mdadm manpages: mdassemble(8), mdmon(8) Christoph Anton Mitterer
2011-03-10 5:18 ` NeilBrown
2011-03-10 13:57 ` Christoph Anton Mitterer [this message]
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=a5e41cc2828ecc385314e30988be9b7d@imap.dd24.net \
--to=calestyo@scientia.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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