From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Git Mailing list <git@vger.kernel.org>
Subject: Re: how exactly can git config section names contain periods?
Date: Fri, 1 Jun 2018 20:02:52 -0400 [thread overview]
Message-ID: <20180602000252.GA25016@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq36y685vx.fsf@gitster-ct.c.googlers.com>
On Sat, Jun 02, 2018 at 08:05:22AM +0900, Junio C Hamano wrote:
> > This has been deprecated since 2011. Maybe it's time to finally get rid
> > of it.
>
> Sure, but is it worth the transition noise?
>
> The way we lightly utter the word "deprecated" around here probably
> does not align well with the way how end-users perceive the word.
> Just marking something deprecated in a corner of the documentation
> set, without actively making an effort to wean the existing users
> off, while happily accepting the existing "deprecated" practice, is
> what we've done.
>
> In those repositories people have with "[foo.bar] key" syntax that
> were created before or after 2011, we first should start issuing a
> "that syntax will no longer be valid---I'll update it for you if you
> want (y/n)?" warning and keep it for a release or three before
> finally removing the "feature".
Yeah, sorry to be unclear: I meant that we should actually start moving
forward on the removal, and I agree that the first step is issuing a
warning.
It may not be worth the transition noise. For the most part historical
oddities like these aren't hurting anybody. On the other hand, people
read the documentation and go "huh?". These kinds of vestigial options
and special cases can add up to clutter the explanations. So I dunno.
-Peff
next prev parent reply other threads:[~2018-06-02 0:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 20:14 how exactly can git config section names contain periods? Robert P. J. Day
2018-06-01 20:50 ` Randall S. Becker
2018-06-01 21:07 ` Jeff King
2018-06-01 21:55 ` Robert P. J. Day
2018-06-01 23:05 ` Junio C Hamano
2018-06-02 0:02 ` Jeff King [this message]
2018-06-02 8:50 ` Robert P. J. Day
2018-06-02 9:26 ` Jeff King
2018-06-03 9:53 ` Robert P. J. Day
2018-06-03 10:35 ` SZEDER Gábor
2018-06-03 10:35 ` Robert P. J. Day
2018-06-04 12:09 ` Jeff King
2018-06-03 10:44 ` Johannes Sixt
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=20180602000252.GA25016@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rpjday@crashcourse.ca \
/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).