From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [pull] retire mandoc syntax
Date: Mon, 3 Oct 2011 15:14:09 +0200 [thread overview]
Message-ID: <20111003131409.GF1982@nb.net.home> (raw)
In-Reply-To: <CAG27Bk2O5ynXup+P_toB4aALK+fumY61tkeEAiLZXKvwrDifTQ@mail.gmail.com>
On Sun, Sep 18, 2011 at 09:38:17PM +0200, Sami Kerola wrote:
> Hi,
>
> This is mostly about retiring mandoc syntax. The util-linux uses groff
> man macros instead.
>
> The following changes since commit 277a6dd53569a409e05316a7bdaed0e78e326762:
>
> mount: check for target before source on remount (2011-09-13 22:59:39 +0200)
>
> are available in the git repository at:
> https://github.com/kerolasa/lelux-utiliteetit manuals
>
> Sami Kerola (15):
> docs: chcpu and readprofile are sysadmin utils
> docs: fix return value table in fsck.8
bug (typo) ... s/36/32/ Fsck canceled by user request
> docs: align vipw.8 with howto-man-page.txt
> docs: align logger.1 with howto-man-page.txt
> docs: align renice.1 with howto-man-page.txt
Note, be careful with schetutils and renice, it does not use
traditional getopt() concept, for example you cannot use
renice -p <pid> -n <priority>
The order of the options is very strict and "[-n] <priority>" has to
be the first argument on the command line. Maybe this rule should be
mentioned in the -n/--priority description in the man page.
> docs: align script.1 with howto-man-page.txt
> docs: align scriptreplay.1 with howto-man-page.txt
the example scriptreplay.1 uses hidden (hardcoded) typescript file
and redirection of stderr, it sucks. What about:
$ script --timing=file.tm file
...
$ scriptreplay --timing file.tm --typescript file
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2011-10-03 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 19:38 [pull] retire mandoc syntax Sami Kerola
2011-10-03 13:14 ` 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=20111003131409.GF1982@nb.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).