From: Stefan Beller <sbeller@google.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
Jacob Keller <jacob.keller@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.11.0-rc0
Date: Tue, 1 Nov 2016 14:10:06 -0700 [thread overview]
Message-ID: <CAGZ79ka6un7nHaNk3F8yp3vFSnB-iGapqLcZ-ZC3EvcKE4DMNQ@mail.gmail.com> (raw)
In-Reply-To: <20161101205916.d74n6lhgp2hexpzr@sigill.intra.peff.net>
On Tue, Nov 1, 2016 at 1:59 PM, Jeff King <peff@peff.net> wrote:
> On Tue, Nov 01, 2016 at 01:56:34PM -0700, Junio C Hamano wrote:
>
>> > As of -rc0, we have both --indent-heuristic and --compaction-heuristic
>> > (along with matching config), and they are mutually exclusive.
>> >
>> > In [1], Stefan suggested just replacing the compaction heuristic
>> > entirely with the new one (and you seemed to agree). If we're going to
>> > do that, it makes sense to do so before the release, so that we don't
>> > get stuck supporting --indent-heuristic forever.
>>
>> You meant "compaction" in the last part? I think it is probably a
>> good idea.
>
> I thought the plan mentioned in the mail I linked was to keep the indent
> heuristic, but simply _call_ it the compaction heuristic. IOW, to swap
> out the implementation under the hood for something we know is better.
AFAICT Michaels design is better in every aspect than what I did initially,
so it supersedes the work I did there. I would support the swap in names.
>
> We've already released a version with --compaction-heuristic, so we are
> stuck keeping it forever either way.
IIRC the release notes specifically noted this flag to be experimental and
may be removed in future versions.
When not doing the swap of the implementation, but rather remove the
experimental feature of compaction-heuristic and introducing a *new*
experimental --indent-heuristic, this may drive the point across that
these names are actually experimental.
next prev parent reply other threads:[~2016-11-01 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 21:49 [ANNOUNCE] Git v2.11.0-rc0 Junio C Hamano
2016-10-31 23:16 ` Simon Ruderich
2016-11-01 9:07 ` Patrick Steinhardt
2016-11-01 20:36 ` Jeff King
2016-11-01 20:56 ` Junio C Hamano
2016-11-01 20:59 ` Jeff King
2016-11-01 21:05 ` Junio C Hamano
2016-11-01 21:38 ` Junio C Hamano
2016-11-01 21:41 ` Stefan Beller
2016-11-01 22:06 ` Junio C Hamano
2016-11-01 21:45 ` Junio C Hamano
2016-11-01 21:50 ` Jeff King
2016-11-02 21:44 ` Michael Haggerty
2016-11-01 21:10 ` Stefan Beller [this message]
2016-11-02 1:21 ` Jacob Keller
2016-11-01 20:43 ` Stefan Beller
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=CAGZ79ka6un7nHaNk3F8yp3vFSnB-iGapqLcZ-ZC3EvcKE4DMNQ@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=mhagger@alum.mit.edu \
--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 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).