From: Oleg Drokin <green@namesys.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Hans Reiser <reiser@namesys.com>,
Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: Getopt improvements
Date: Fri, 28 Feb 2003 10:04:54 +0300 [thread overview]
Message-ID: <20030228100454.B878@namesys.com> (raw)
In-Reply-To: <3E5EAA3A.8030203@suse.com>
Hello!
On Thu, Feb 27, 2003 at 07:15:54PM -0500, Jeff Mahoney wrote:
> Well, the more possible values a given multivalue option has, the more
> values that need to be explicitly negated for a mutually exclusive
> option. The descriptor lines get quite long with more than 2 options
> when you need to specify every value you need to clear.
That's true. Not sure we can do something about that.
> I also got to thinking that perhaps the idea of being able to specify
> multiple values for multivalue options isn't that great. If more than
> one value is possible, the option should probably be a first level
> option (ie: -ooption) rather than a second level option (ie:
> -oname=value). With that in mind, I'd prefer to see my original
> implementation used.
Well, we have two kinds of tails now, large and small.
So do you propose we should have:
notail
smalltail
largetail options?
please keep in mind that smalltail and largetail are mutually exclusive.
Bye,
Oleg
next prev parent reply other threads:[~2003-02-28 7:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 20:42 Getopt improvements Jeff Mahoney
2003-02-26 21:10 ` Hans Reiser
2003-02-27 6:25 ` Oleg Drokin
2003-02-27 15:39 ` Jeff Mahoney
2003-02-27 16:25 ` Oleg Drokin
2003-02-27 20:20 ` Hans Reiser
2003-02-27 21:35 ` Jeff Mahoney
2003-02-27 22:35 ` Hans Reiser
2003-02-28 0:15 ` Jeff Mahoney
2003-02-28 0:22 ` Anders Widman
2003-02-28 7:47 ` Oleg Drokin
2003-02-28 7:04 ` Oleg Drokin [this message]
[not found] ` <3E5F634D.8060901@suse.com>
2003-02-28 13:54 ` Oleg Drokin
2003-02-28 7:01 ` Oleg Drokin
2003-02-28 12:04 ` Hans Reiser
2003-02-28 12:41 ` Oleg Drokin
2003-02-28 12:52 ` Hans Reiser
2003-02-28 13:15 ` Oleg Drokin
2003-02-28 13:26 ` Jeff Mahoney
2003-02-28 15:30 ` Jeff Mahoney
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=20030228100454.B878@namesys.com \
--to=green@namesys.com \
--cc=jeffm@suse.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.