From: Karel Zak <kzak@redhat.com>
To: Martin Steigerwald <ms@teamix.de>
Cc: util-linux@vger.kernel.org
Subject: Re: chrt: inconsistency in --help
Date: Tue, 9 Jun 2015 11:24:12 +0200 [thread overview]
Message-ID: <20150609092412.GG1992@ws.net.home> (raw)
In-Reply-To: <716925135.onXIMLDpa0@merkaba>
On Tue, Jun 09, 2015 at 10:37:46AM +0200, Martin Steigerwald wrote:
> Suggestion:
>
> 1) Either make chrt command parsing more flexible (preffered)
Unfortunately we have to care about backward compatibility...
> 2) or or even and change set policy to
>
> Set policy:
> chrt [options] [-p] [<policy>] <priority> [<pid> | <command> [<arg>...]]
Yes, I have modified --help output to this
> But well second option separates -p from pid. So maybe option 1 is the way
> to go.
It's not elegant, but unfortunately used for years and I don't think
we want to make it more complex by any improvement.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-06-09 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 8:37 chrt: inconsistency in --help Martin Steigerwald
2015-06-09 9:24 ` Karel Zak [this message]
2015-06-11 9:03 ` Benno Schulenberg
2015-06-15 13:09 ` Karel Zak
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=20150609092412.GG1992@ws.net.home \
--to=kzak@redhat.com \
--cc=ms@teamix.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