From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Rune Philosof <rune@philosof.dk>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Complain in the tests about git config not failing with, keys without a section
Date: Mon, 05 Mar 2012 11:29:10 -0800 [thread overview]
Message-ID: <7veht626ex.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120305103714.GA30463@sigill.intra.peff.net> (Jeff King's message of "Mon, 5 Mar 2012 05:37:14 -0500")
Jeff King <peff@peff.net> writes:
> For "git config --list", as you noticed, we include it in the output. I
> suspect we should simply omit it as cruft. But we could also issue a
> warning, and/or die.
A new warning might be worth if we were to suddenly start omitting
them from --list output, but dying won't fly well.
People have been happily lived with their config with such lines
that do not affect what git does, but a new version of git starts to
"die" on them. For what purpose? Whom is such a change designed to
help?
next prev parent reply other threads:[~2012-03-05 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 10:57 [PATCH 1/2] Complain in the tests about git config not failing with, keys without a section Rune Schjellerup Philosof
2012-03-02 18:40 ` Junio C Hamano
2012-03-05 7:59 ` Rune Philosof
2012-03-05 10:37 ` Jeff King
2012-03-05 19:29 ` Junio C Hamano [this message]
2012-03-06 8:06 ` Jeff King
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=7veht626ex.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rune@philosof.dk \
/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).