path: root/wt-status.c
diff options
authorLinus Torvalds <>2007-09-14 17:39:48 (GMT)
committerJunio C Hamano <>2007-09-14 19:12:57 (GMT)
commit0024a54923a12f8c05ce4290f5ebefab0cce4336 (patch)
tree751821e1d91ecd4c8579fe581d57ebd0d99b1e4e /wt-status.c
parentb78281f7215c0236da6bd5c04ec5e500c83fd101 (diff)
Fix the rename detection limit checking
This adds more proper rename detection limits. Instead of just checking the limit against the number of potential rename destinations, we verify that the rename matrix (which is what really matters) doesn't grow ridiculously large, and we also make sure that we don't overflow when doing the matrix size calculation. This also changes the default limits from unlimited, to a rename matrix that is limited to 100 entries on a side. You can raise it with the config entry, or by using the "-l<n>" command line flag, but at least the default is now a sane number that avoids spending lots of time (and memory) in situations that likely don't merit it. The choice of default value is of course very debatable. Limiting the rename matrix to a 100x100 size will mean that even if you have just one obvious rename, but you also create (or delete) 10,000 files, the rename matrix will be so big that we disable the heuristics. Sounds reasonable to me, but let's see if people hit this (and, perhaps more importantly, actually *care*) in real life. Signed-off-by: Linus Torvalds <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'wt-status.c')
1 files changed, 1 insertions, 0 deletions
diff --git a/wt-status.c b/wt-status.c
index 5205420..10ce6ee 100644
--- a/wt-status.c
+++ b/wt-status.c
@@ -227,6 +227,7 @@ static void wt_status_print_updated(struct wt_status *s)
rev.diffopt.format_callback = wt_status_print_updated_cb;
rev.diffopt.format_callback_data = s;
rev.diffopt.detect_rename = 1;
+ rev.diffopt.rename_limit = 100;
run_diff_index(&rev, 1);