public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: Util-Linux <util-linux@vger.kernel.org>, Davidlohr Bueso <dave@gnu.org>
Subject: Re: [patches] a bunch of man-page fixes, plus -V for blkid
Date: Wed, 20 Mar 2013 14:11:39 +0100	[thread overview]
Message-ID: <20130320131139.GE14833@x2.net.home> (raw)
In-Reply-To: <1363639067.25811.140661206020553.0C776E64@webmail.messagingengine.com>

On Mon, Mar 18, 2013 at 09:37:47PM +0100, Benno Schulenberg wrote:
> Attached bunch of patches mainly normalizes the formatting of the

 All applied, thanks.

> man pages in the misc-utils directory.  The second patch adds -V for
> --version to the blkid command (instead of just -v).  And the seventh
> patch makes the section AVAILABILITY always be the last one in all
> man pages.
> 
> CC'ing Davidlohr because the sixth patch touches the man page of
> his lslocks command.  This man page makes a reference to chmod(1),
> but on my machine chmod(1) does not say anything about lock files,
> nor anything about being mandatory or advisory -- only fcntl(2) does.
> So I have changed that reference, but am unsure whether this is
> okay.  The man page also referes to lockf(2), but on my machine
> there is only a lockf(3); so I've changed that one too, but again am
> unsure whether it is okay.  Davidlohr?

 Heh.. where is David, that's the question :-)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      reply	other threads:[~2013-03-20 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 20:37 [patches] a bunch of man-page fixes, plus -V for blkid Benno Schulenberg
2013-03-20 13:11 ` Karel Zak [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=20130320131139.GE14833@x2.net.home \
    --to=kzak@redhat.com \
    --cc=bensberg@justemail.net \
    --cc=dave@gnu.org \
    --cc=util-linux@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