git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] git config: clarify bool types
Date: Mon, 12 Oct 2009 13:03:35 +0300	[thread overview]
Message-ID: <94a0d4530910120303y205e6cfeg80ba0dfd6ed5a045@mail.gmail.com> (raw)
In-Reply-To: <7v7hv1kxyg.fsf@alter.siamese.dyndns.org>

On Mon, Oct 12, 2009 at 8:01 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> The value is what it is, the --bool and --bool-or-int options don't
>> specify the value type, just how it is interpreted. For example: a value
>> of '1' can be interpreted as 'true'.
>
> It is not really about "interpreting", but about showing, isn't it?

Unless you are setting it, instead of reading it.

-- 
Felipe Contreras

  reply	other threads:[~2009-10-12 10:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11 20:46 [PATCH 0/3] Trivial patches Felipe Contreras
2009-10-11 20:46 ` [PATCH 1/3] Fix a bunch of pointer declarations (codestyle) Felipe Contreras
2009-10-11 20:46   ` [PATCH 2/3] git config: clarify bool types Felipe Contreras
2009-10-11 20:46     ` [PATCH 3/3] user-manual: use 'fast-forward' Felipe Contreras
2009-10-12  5:05       ` Junio C Hamano
2009-10-12 10:05         ` Felipe Contreras
2009-10-12 12:50           ` Michael J Gruber
2009-10-12  5:01     ` [PATCH 2/3] git config: clarify bool types Junio C Hamano
2009-10-12 10:03       ` Felipe Contreras [this message]
2009-10-12 12:30         ` Michael J Gruber
2009-10-12 17:14           ` Felipe Contreras
2009-10-13  7:09             ` Michael J Gruber
2009-10-13 10:02               ` Felipe Contreras
2009-10-11 20:53   ` [PATCH 1/3] Fix a bunch of pointer declarations (codestyle) Thiago Farina
2009-10-11 20:56     ` Felipe Contreras

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=94a0d4530910120303y205e6cfeg80ba0dfd6ed5a045@mail.gmail.com \
    --to=felipe.contreras@gmail.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).