From: "Anand Kumria" <wildfire@progsoc.org>
To: git@vger.kernel.org
Subject: Re: On boolean configuration variables...
Date: Sun, 25 Jun 2006 13:33:26 +0000 (UTC) [thread overview]
Message-ID: <e7m3b6$eoa$1@sea.gmane.org> (raw)
In-Reply-To: 7vy7vmviul.fsf@assigned-by-dhcp.cox.net
On Sat, 24 Jun 2006 05:28:02 -0700, Junio C Hamano wrote:
> Boolean configuration variables in $GIT_DIR/config are a bit
> strange.
>
> [bool]
> var1
> var2 =
> var3 = true
> var4 = yes
> var5 = 1
> var6 = 2
> var7 = false
> var8 = no
> var9 = 0
>
> var1, var3, var5, and var6 are "true"; var2, var7 and var9 are
> "false". var4 and var8 are syntax errors.
>
> Currently "git repo-config --bool --get bool.var1" returns
> "false", which is fixed by the attached patch, but I am
> wondering if it is a good idea to allow "yes" and "no" as well.
>
Allowing 'yes' and 'no' to equal 'true' and 'false' respectively sounds
pretty sane and user-friendly.
Why wouldn't you want to do that?
Anand
next prev parent reply other threads:[~2006-06-25 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 12:28 On boolean configuration variables Junio C Hamano
2006-06-25 13:33 ` Anand Kumria [this message]
2006-06-25 14:00 ` Johannes Schindelin
2006-06-25 15:41 ` Anand Kumria
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='e7m3b6$eoa$1@sea.gmane.org' \
--to=wildfire@progsoc.org \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).