From: Karel Zak <kzak@redhat.com>
To: "Voelker, Bernhard" <bernhard.voelker@siemens-enterprise.com>
Cc: Davidlohr Bueso <dave@gnu.org>,
Bernhard Voelker <mail@bernhard-voelker.de>,
"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>
Subject: Re: [PATCH 13/15] prlimit: enhance examples section of the man page
Date: Wed, 16 Nov 2011 14:05:51 +0100 [thread overview]
Message-ID: <20111116130551.GK7916@nb.net.home> (raw)
In-Reply-To: <7856072A9D04C24B82DFE2B1112FE38A0D86D86AB2@MCHP058A.global-ad.net>
On Mon, Nov 14, 2011 at 10:24:14AM +0100, Voelker, Bernhard wrote:
> Davidlohr Bueso wrote:
> > On Mon, 2011-11-14 at 02:48 +0100, Bernhard Voelker wrote:
> > > [PATCH 13/15] prlimit: enhance examples section of the man page
> > >
> > > Add various examples to the man page, e.g. demonstrating setting
> > > limits using short options, showing that the --pid option can be
> > > used in random positions, how to use the "-1" notation for the
> > > "unlimited" value, and that prlimit takes the values from the arguments
> > > last set.
>
> > Just a few examples are more than enough to illustrate the point;
> > manpages have always been this way. I think this is unnecessary and
> > clogs the document.
>
> admitted.
>
> Somehow I felt that the existing examples where to homogeneous.
This is feature ;-)
Really, we prefer nice *readable* examples with long options.
> Well, prlimit didn't e.g. support passing the PID after other
> modifying arguments, so I thought that enhancing the examples
> with the new, "wilder" usage would be nice. ;-)
>
> But in these 2 I missed an error: there's a "=" missing between
> "--pid" and the PID:
>
> > > -.IP "\fBprlimit \-\-pid 13134 \--rss --nofile=1024:4095\fP"
> > > +.IP "\fBprlimit \--rss \-\-pid 13134 --nofile=1024:4095\fP"
>
> > > -.IP "\fBprlimit \-\-pid 13134 --nproc=512:\fP"
> > > +.IP "\fBprlimit \-\-pid 13134 -n512:\fP"
>
> I only spotted the missing "=" here, but failed to mention it
> in the commit log:
>
> > > -.IP "\fBprlimit \-\-pid $$ --nproc=unlimited\fP"
> > > +.IP "\fBprlimit \-\-pid=$$ --nproc=unlimited\fP"
>
> What's your recommendation?
The '=' is necessary for optional arguments (for example resource
arguments) only.
Bernhard, small note: many of your patches are malformed by your
e-mail client. Please, reconfigure the mail client (to not modify
long lines) or use git-send-email.
Thanks, your found many issues!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-11-16 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 1:48 [PATCH 13/15] prlimit: enhance examples section of the man page Bernhard Voelker
2011-11-14 10:50 ` Davidlohr Bueso
2011-11-14 9:24 ` Voelker, Bernhard
2011-11-16 13:05 ` Karel Zak [this message]
2011-11-16 14:15 ` Bernhard Voelker
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=20111116130551.GK7916@nb.net.home \
--to=kzak@redhat.com \
--cc=bernhard.voelker@siemens-enterprise.com \
--cc=dave@gnu.org \
--cc=mail@bernhard-voelker.de \
--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