Re: warning: too many files, skipping inexact rename detection

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Jeff King
Date: Saturday, April 26, 2008 - 6:57 am

On Sat, Apr 26, 2008 at 06:32:09AM -0700, Andrew Morton wrote:


Rename detection is O(n^2), so when it looks like it will take a really
long time, we skip it. This has been happening for a while, but 1.5.5
only recently started telling the user (based on some people wondering
why renames weren't found during their enormous merges).

The default rename limit is 100, but you can bump it via the
diff.renamelimit config option. A few tests that I did imply that
200-400 is reasonable for logging, and 800-1000 for a merge:

  http://article.gmane.org/gmane.comp.version-control.git/73519

Are you running into actual problems with rename detection, or is the
message just too scary and confusing?

-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: warning: too many files, skipping inexact rename detection, Jeff King, (Sat Apr 26, 6:57 am)
[PATCH 0/3] rename limit improvements, Jeff King, (Wed Apr 30, 10:21 am)
[PATCH 1/3] add merge.renamelimit config option, Jeff King, (Wed Apr 30, 10:23 am)
[PATCH 2/3] bump rename limit defaults, Jeff King, (Wed Apr 30, 10:24 am)
Re: [PATCH 1/3] add merge.renamelimit config option, Jeff King, (Wed Apr 30, 11:18 am)
Re: [PATCH 1/3] add merge.renamelimit config option, Junio C Hamano, (Sat May 3, 1:15 pm)
Re: [PATCH 1/3] add merge.renamelimit config option, Jeff King, (Sun May 4, 12:31 pm)