From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Junio C Hamano <gitster@pobox.com>,
Martin Langhoff <martin.langhoff@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 2/4] bump rename limit defaults (again)
Date: Sun, 20 Feb 2011 05:12:47 -0500 [thread overview]
Message-ID: <20110220101247.GD988@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTi=aWC_sXK1VBspsiVAwhkC4pP8Z+uq7QceLMopS@mail.gmail.com>
On Sat, Feb 19, 2011 at 09:12:49PM +0100, Ævar Arnfjörð Bjarmason wrote:
> On Sat, Feb 19, 2011 at 11:21, Jeff King <peff@peff.net> wrote:
>
> > Let's bump the diff/merge default limits from 200/500 to
> > 400/1000. Those are 2 seconds and 10 seconds respectively on
> > my modern hardware.
>
> This is somewhat outside the scope of your patch, but rather than
> making these decisions for the user and compiling them into Git
> wouldn't it be better to expose it somehow?
What do you mean by expose it? We already have config options; this is
just for the defaults.
Or do you mean allowing setting merge.renamelimits to "30s" and cutting
off detection after 30 seconds? I think that would be a reasonable idea,
though part of me doesn't like non-deterministic answers based on how
loaded the system is.
> E.g. when you do a git-merge show a progress bar (similar to
> git-clone) showing that we're trying to do rename detection, show that
> we stopped, and when we fail point out that the user could run
> git-merge with some switch that would make Git try harder.
Er, isn't that exactly what patches 1/4 and 4/4 in my series do?
-Peff
next prev parent reply other threads:[~2011-02-20 10:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 18:58 Merging limitations after directory renames -- interesting test repo Martin Langhoff
2011-02-18 22:21 ` Jeff King
2011-02-18 23:27 ` Linus Torvalds
2011-02-19 0:26 ` Linus Torvalds
2011-02-19 0:52 ` Junio C Hamano
2011-02-19 1:03 ` Linus Torvalds
2011-02-19 1:20 ` Linus Torvalds
2011-02-19 0:55 ` Linus Torvalds
2011-02-19 0:44 ` Junio C Hamano
2011-02-19 9:08 ` Jeff King
2011-02-19 10:19 ` Jeff King
2011-02-19 10:20 ` [PATCH 1/4] merge: improve inexact rename limit warning Jeff King
2011-02-21 23:33 ` Junio C Hamano
2011-02-22 15:39 ` Jeff King
2011-02-22 18:46 ` Junio C Hamano
2011-02-23 8:02 ` Jeff King
2011-02-19 10:21 ` [PATCH 2/4] bump rename limit defaults (again) Jeff King
2011-02-19 17:54 ` Piotr Krukowiecki
2011-02-20 10:10 ` Jeff King
2011-02-19 20:12 ` Ævar Arnfjörð Bjarmason
2011-02-20 10:12 ` Jeff King [this message]
2011-02-19 10:21 ` [PATCH 3/4] commit: stop setting rename limit Jeff King
2011-02-19 10:25 ` [RFC/PATCH 4/4] inexact rename detection eye candy Jeff King
2011-02-19 15:57 ` Linus Torvalds
2011-02-20 9:48 ` Jeff King
2011-02-20 9:51 ` [PATCH 1/3] add inexact rename detection progress infrastructure Jeff King
2011-02-20 9:53 ` [PATCH 2/3] merge: enable progress reporting for rename detection Jeff King
2011-02-20 9:56 ` [PATCH 3/3] pull: propagate --progress to merge Jeff King
2011-02-20 10:37 ` [RFC/PATCH 4/4] inexact rename detection eye candy Jeff King
2011-02-19 16:29 ` Martin Langhoff
2011-02-20 10:04 ` Jeff King
2011-02-20 13:16 ` Martin Langhoff
2011-02-19 15:22 ` Merging limitations after directory renames -- interesting test repo Martin Langhoff
2011-02-19 15:31 ` Martin Langhoff
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=20110220101247.GD988@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.langhoff@gmail.com \
--cc=torvalds@linux-foundation.org \
/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).