From: Jeff King <peff@peff.net>
To: Stefan Beller <sbeller@google.com>
Cc: "Alex Prengère" <alexprengere@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] add--interactive: respect diff.compactionHeuristic
Date: Thu, 16 Jun 2016 19:40:43 -0400 [thread overview]
Message-ID: <20160616234043.GC15013@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGZ79kaPVFT=yeSAkmf55+qXcCgMkwpgkC8jXhuZvqj5mWtgLw@mail.gmail.com>
On Thu, Jun 16, 2016 at 09:50:45AM -0700, Stefan Beller wrote:
> > -- >8 --
> > Subject: add--interactive: respect diff.compactionHeuristic
> >
> > We use plumbing to generate the diff, so it doesn't
> > automatically pick up UI config like compactionHeuristic.
> > Let's forward it on, since interactive adding is porcelain.
> >
> > Note that we only need to handle the "true" case. There's no
> > point in passing --no-compaction-heuristic when the variable
> > is false, since nothing else could have turned it on.
>
> because we don't want to implement --[no-]compaction-heuristic
> as a command line switch to git-add?
> Fine with me.
We could, but I don't think it is worth the effort (and anyway, it would
override the config :) ).
> Stepping back and looking how the compaction heuristic turned out,
> I think this is what we did not want to see, i.e. the need to bring it in
> every command, but rather enable and release it. But we backed off
> of the default-on, and now people may ask for the --no-compaction-heuristic
> in interactive add eventually, when they run into a corner case.
Yeah, I'm not excited to be plumbing it through, especially if we just
end up flipping it on by default. But perhaps people would still want to
be able to do the opposite (turning it off for a specific case via the
config). I dunno.
> For now:
> Reviewed-by: Stefan Beller <sbeller@google.com>
Thanks.
-Peff
prev parent reply other threads:[~2016-06-16 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 14:22 compactionHeuristic=true is not used by interactive staging Alex Prengère
2016-06-14 21:42 ` Jeff King
2016-06-14 21:45 ` Junio C Hamano
2016-06-15 6:24 ` Alex Prengère
2016-06-16 12:27 ` [PATCH] add--interactive: respect diff.compactionHeuristic Jeff King
2016-06-16 16:50 ` Stefan Beller
2016-06-16 23:40 ` Jeff King [this message]
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=20160616234043.GC15013@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=alexprengere@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.com \
/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).