git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Arnott <andrewarnott@gmail.com>, git@vger.kernel.org
Subject: Re: Intensive rename detection
Date: Mon, 3 Nov 2008 23:31:33 -0500	[thread overview]
Message-ID: <20081104043133.GB31276@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0811032021210.3419@nehalem.linux-foundation.org>

On Mon, Nov 03, 2008 at 08:22:34PM -0800, Linus Torvalds wrote:

> How many renames do you have? Modern versions of git will do any number of 
> exact renames, but the (rather expensive) inexact rename detection has a 
> default limit of something fairly small.

I was about to say "git should have complained about turning off the
requested rename detection", but I forgot that we silenced that warning
except for merges.

Maybe it makes sense for "status" or a single "diff" (but definitely not
"log", where it isn't even clear which diff caused it!). I dunno. I find
it clutter for anything except a merge, but if that is in fact what is
happening here, it might have produced one slightly less confused user.

-Peff

  parent reply	other threads:[~2008-11-04  4:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <216e54900811031717j70669868p3c7503357ceb5138@mail.gmail.com>
2008-11-04  1:18 ` Intensive rename detection Andrew Arnott
2008-11-04  1:39   ` Junio C Hamano
2008-11-04  4:22   ` Linus Torvalds
2008-11-04  4:23     ` Linus Torvalds
2008-11-04  4:31     ` Jeff King [this message]
     [not found]     ` <216e54900811032107p159e98ecn8958f0a78efde8f2@mail.gmail.com>
2008-11-04  5:19       ` Andrew Arnott
2008-11-04  6:02         ` Andrew Arnott
2008-11-04  6:16           ` Jeff King
2008-11-04  6:36             ` Andrew Arnott
2008-11-04 10:47               ` Björn Steinbrink
2008-11-05  3:22               ` Jeff King

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=20081104043133.GB31276@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=andrewarnott@gmail.com \
    --cc=git@vger.kernel.org \
    --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).