From: Phil Muldoon <pmuldoon@redhat.com>
To: Nurdin Premji <npremji@redhat.com>
Cc: frysk <frysk@sources.redhat.com>
Subject: Re: Command line utilities argument types.
Date: Fri, 01 Jun 2007 19:13:00 -0000 [thread overview]
Message-ID: <46606F89.5050805@redhat.com> (raw)
In-Reply-To: <46606E0E.3050804@redhat.com>
Nurdin Premji wrote:
> I'm going to be refactoring how the command line utilities will parse
> their arguments to make them as unified as possible.
>
> I've identified 4 types of input that can be passed to a command line
> utility: Pids, Core files, a command (executable with options), or
> nothing.
>
> Here is my interpretation of which command line utilities can take
> what types of arguments.
How would you classify options (like logging and other behavior
modifiers, like -a for all maps output for fcore)? Or is that not going
to be touched by this refactor?.
FWIW fcore can take one or many pids, can take logging options and can
take an optional -a parameter to dump all maps instead of selecting the
maps based on historical precedence of what to write/what to elide.
Regards
Phil
next prev parent reply other threads:[~2007-06-01 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 19:12 Nurdin Premji
2007-06-01 19:13 ` Phil Muldoon [this message]
2007-06-01 21:33 ` Nurdin Premji
2007-06-01 20:34 ` Nurdin Premji
2007-06-01 21:05 ` Andrew Cagney
2007-06-02 1:10 ` Nurdin Premji
2007-06-09 17:57 ` Nurdin Premji
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=46606F89.5050805@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@sources.redhat.com \
--cc=npremji@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).