From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Lars Schneider <larsxschneider@gmail.com>
Subject: Re: 2.11.0-rc1 will not be tagged for a few days
Date: Wed, 09 Nov 2016 15:40:17 -0800 [thread overview]
Message-ID: <xmqqshr06x3y.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20161108004038.a7gyoe6wpucxjmvz@sigill.intra.peff.net> (Jeff King's message of "Mon, 7 Nov 2016 19:40:38 -0500")
Jeff King <peff@peff.net> writes:
> I think we also need to make a final decision on the indent/compaction
> heuristic naming. After reading Michael's [0], and the claim by you and
> Stefan that the "compaction" name was declared sufficiently experimental
> that we could later take it away, I'm inclined to follow this plan:
>
> 1. Ship v2.11 with what is in master; i.e., both compaction and indent
> heuristics, triggerable by config or command line.
>
> 2. Post-v2.11, retire the compaction heuristic as a failed experiment.
> Keeping it in v2.11 doesn't hurt anything (it was already
> released), and lets us take our time coming up with and cooking the
> patch.
>
> 3. Post-v2.11, flip the default for diff.indentHeuristic to "true".
> Keep at least the command line option around indefinitely for
> experimenting (i.e., "this diff looks funny; I wonder if
> --no-indent-heuristic makes it look better").
>
> Config option can either stay or go at that point. I have no
> preference.
>
> The nice thing about that plan is it punts on merging any new code to
> post-v2.11. :)
OK, I can go with that plan. Thanks for an outline.
next prev parent reply other threads:[~2016-11-09 23:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 2:32 2.11.0-rc1 will not be tagged for a few days Junio C Hamano
2016-11-08 0:40 ` Jeff King
2016-11-08 6:25 ` Johannes Sixt
2016-11-08 21:48 ` Jeff King
2016-11-09 6:29 ` Junio C Hamano
2016-11-09 16:51 ` Jeff King
2016-11-09 23:35 ` Junio C Hamano
2016-11-09 23:40 ` Junio C Hamano [this message]
2016-11-10 21:43 ` Junio C Hamano
2016-11-11 0:26 ` Junio C Hamano
2016-11-11 16:13 ` Johannes Schindelin
2016-11-11 17:02 ` Johannes Schindelin
2016-11-11 17:05 ` Lars Schneider
2016-11-11 17:31 ` Lars Schneider
2016-11-11 17:38 ` Lars Schneider
2016-11-11 20:44 ` Johannes Sixt
2016-11-11 20:52 ` Junio C Hamano
2016-11-11 21:07 ` Junio C Hamano
2016-11-11 21:22 ` Johannes Sixt
2016-11-12 13:33 ` Lars Schneider
2016-11-11 17:41 ` 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=xmqqshr06x3y.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.