From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Pierre Habouzit <madcoder@debian.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
git@vger.kernel.org
Subject: Re: [PATCH] config: deprecate using "" as boolean value false.
Date: Mon, 11 Feb 2008 00:21:26 -0800 [thread overview]
Message-ID: <7vskzzaoop.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080211082216.e9212310.chriscool@tuxfamily.org> (Christian Couder's message of "Mon, 11 Feb 2008 08:22:16 +0100")
Why do you call this a "fix", when the only effect of it is
breaking people's existing setups? Wouldn't a set of proper
fixes to the config parsing callback functions solve all the
issues without having any downsides?
I think you are wasting both of our times. You could be doing
the real fix instead. Or I could be spending time on it,
instead of repeating to you how mistaken this approach is.
So far I've seen and queued only two usable fixes since that
[Janitor] request. Maybe I should have ignored all this
discussion in this thread and spent my time on doing the
Janitorial work. The reason I joined the thread was that I
hoped that I could save people like _you_ from wasting _your_
time in the discussion, instead of making better use of it by
doing audits and fixes.
Grrr.
next prev parent reply other threads:[~2008-02-11 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 7:22 [PATCH] config: deprecate using "" as boolean value false Christian Couder
2008-02-11 8:21 ` Junio C Hamano [this message]
2008-02-11 8:46 ` Junio C Hamano
2008-02-11 9:22 ` [PATCH] teach config parsers to diagnose missing values 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=7vskzzaoop.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=madcoder@debian.org \
--cc=torvalds@linux-foundation.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).