git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Beller <stefanbeller@googlemail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Remove deprecated OPTION_BOOLEAN
Date: Mon, 29 Jul 2013 20:18:51 +0200	[thread overview]
Message-ID: <51F6B20B.1010709@googlemail.com> (raw)
In-Reply-To: <7v4nbd1bjj.fsf@alter.siamese.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]

On 07/29/2013 08:11 PM, Junio C Hamano wrote:
> Stefan Beller <stefanbeller@googlemail.com> writes:
> 
>> As of b04ba2bb4 OPTION_BOOLEAN was deprecated.
> 
> The primary purpose of b04ba2bb (parse-options: deprecate
> OPT_BOOLEAN, 2011-09-27) is to deprecate OPT_BOOLEAN(), which was
> hard to use correctly.
> 
> OPT_BOOLEAN() is not touched at all with this patch, it seems.  Do
> they want count-up semantics?
> 

I'm working on the OPT_BOOLEAN replacement as well, but the 
OPTION_BOOLEAN seemed as an easier start (way less until completion)

> At first glance, it looked to me that OPT_HIDDEN_BOOL was a good
> addition, given how often we have PARSE_OPT_HIDDEN.  While I think
> some of the hidden ones are justified, I am not sure if the hiding
> of many options are.  If we stop hiding many of them, HIDDEN_BOOL
> may become not so useful.  I dunno.

There should be no change in semantics.
All those which now use the OPT_HIDDEN_BOOL have had 
{OPTION_BOOLEAN,..., PARSE_OPT_HIDDEN}
before.

But your concern sounds more like you'd dislike the
appearance of OPT_HIDDEN_BOOL because you'd want to remove the
hidden options. The options being hidden there sound to me as if
those were hidden due to their historical nature and there is always
a non-hidden equivalent being better worded.

Stefan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

  reply	other threads:[~2013-07-29 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 15:38 [PATCH] Remove deprecated OPTION_BOOLEAN Stefan Beller
2013-07-29 15:38 ` Stefan Beller
2013-07-29 18:11   ` Junio C Hamano
2013-07-29 18:18     ` Stefan Beller [this message]
2013-07-29 17:58 ` Junio C Hamano
2013-07-29 18:04   ` Stefan Beller
2013-07-29 18:50     ` Junio C Hamano

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=51F6B20B.1010709@googlemail.com \
    --to=stefanbeller@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 NNTP newsgroup(s).