From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC/PATCH] rename: warn user when we have turned off rename detection
Date: Fri, 29 Feb 2008 23:35:00 -0800 [thread overview]
Message-ID: <7vtzjq6gnv.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080301061431.GA27301@coredump.intra.peff.net> (Jeff King's message of "Sat, 1 Mar 2008 01:14:31 -0500")
Jeff King <peff@peff.net> writes:
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> This was another patch from late in the freeze period. It was in
> response to a user getting confused about why rename detection wasn't
> happening in a large merge. Is it appropriate to print this for every
> rename we try? Or should it just be for merges?
>
> Perhaps we should also bump the default limit from 100, which I think
> was just arbitrarily chosen.
> ...
> + if ((num_create > rename_limit && num_src > rename_limit) ||
> + (num_create * num_src > rename_limit * rename_limit)) {
> + warning("too many files, skipping inexact rename detection");
> goto cleanup;
> + }
>
> mx = xmalloc(sizeof(*mx) * num_create * num_src);
> for (dst_cnt = i = 0; i < rename_dst_nr; i++) {
This reminds me of the 6d24ad9 (Optimize rename detection for a huge diff)
topic that reduces the above allocation greatly. Some benching with the
patch may prove useful to establish much higher limits, I suspect.
next prev parent reply other threads:[~2008-03-01 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 6:14 [RFC/PATCH] rename: warn user when we have turned off rename detection Jeff King
2008-03-01 7:35 ` Junio C Hamano [this message]
2008-03-01 8:18 ` Jeff King
2008-03-01 9:30 ` Junio C Hamano
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=7vtzjq6gnv.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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).