From: Joe Perches <joe@perches.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] get_maintainer: add --no-foo options to --help
Date: Wed, 14 Oct 2015 10:38:19 -0700 [thread overview]
Message-ID: <1444844299.2718.26.camel@perches.com> (raw)
In-Reply-To: <20151014173302.GA108923@google.com>
On Wed, 2015-10-14 at 10:33 -0700, Brian Norris wrote:
> + akpm
>
> On Wed, Oct 14, 2015 at 10:15:31AM -0700, Joe Perches wrote:
> > On Wed, 2015-10-14 at 10:10 -0700, Brian Norris wrote:
> > > Ping? Should I resend?
> >
> > I don't have a strong opinion about this.
> >
> > It seems the [no] blocks make the generic options more
> > difficult to read.
>
> The '[no]' formatting is similar to how some (but not all) man pages do
> this. If it is too difficult, I'm open to something else. Just a note
> somewhere that all boolean options have equivalent '--no<foo>' options?
>
> BTW, one thing I didn't note in the commit message is that this is
> important because some options are already *on* by default, and so it is
> only sensible to use the --no version, which isn't even documented.
> Particularly, options like --norolestats.
Maybe using something like gcc's documentation of options
that have negative forms might be better.
$ man gcc
...
Most of these have both positive and negative forms;
the negative form of -ffoo is -fno-foo
...
$
prev parent reply other threads:[~2015-10-14 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 22:09 [PATCH 1/2] get_maintainer: add --no-foo options to --help Brian Norris
2015-08-19 22:09 ` [PATCH 2/2] get_maintainer: add missing documentation for --[no]git-blame-signatures Brian Norris
2015-10-14 17:10 ` [PATCH 1/2] get_maintainer: add --no-foo options to --help Brian Norris
2015-10-14 17:15 ` Joe Perches
2015-10-14 17:33 ` Brian Norris
2015-10-14 17:38 ` Joe Perches [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=1444844299.2718.26.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@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