git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Andrew Morton <akpm@linux-foundation.org>, git@vger.kernel.org
Subject: Re: [PATCH 1/3] add merge.renamelimit config option
Date: Sat, 03 May 2008 13:15:06 -0700	[thread overview]
Message-ID: <7viqxvta9h.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080430172354.GA23747@sigill.intra.peff.net> (Jeff King's message of "Wed, 30 Apr 2008 13:23:55 -0400")

Jeff King <peff@peff.net> writes:

> diff --git a/builtin-merge-recursive.c b/builtin-merge-recursive.c
> index 910c0d2..1293e3d 100644
> --- a/builtin-merge-recursive.c
> +++ b/builtin-merge-recursive.c
> @@ -361,7 +362,9 @@ static struct path_list *get_renames(struct tree *tree,
>  	diff_setup(&opts);
>  	DIFF_OPT_SET(&opts, RECURSIVE);
>  	opts.detect_rename = DIFF_DETECT_RENAME;
> -	opts.rename_limit = rename_limit;
> +	opts.rename_limit = merge_rename_limit >= 0 ? merge_rename_limit :
> +			    diff_rename_limit >= 0 ? diff_rename_limit :
> +			    100;
>  	opts.output_format = DIFF_FORMAT_NO_OUTPUT;
>  	if (diff_setup_done(&opts) < 0)
>  		die("diff setup failed");

Makes one wonder where the magic 100 comes from.  Wouldn't this

	opts.rename_limit = (merge_rename_limit >= 0)
        		  ? merge_rename_limit
                          : diff_rename_limit;

be easier to maintain, with the same semantics?

  parent reply	other threads:[~2008-05-03 20:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 13:32 warning: too many files, skipping inexact rename detection Andrew Morton
2008-04-26 13:57 ` Jeff King
2008-04-26 14:06   ` Andrew Morton
2008-04-26 14:52     ` Jeff King
2008-04-30 17:21       ` [PATCH 0/3] rename limit improvements Jeff King
2008-04-30 17:23         ` [PATCH 1/3] add merge.renamelimit config option Jeff King
2008-04-30 18:18           ` Jeff King
2008-05-03 20:15           ` Junio C Hamano [this message]
2008-05-04 19:31             ` Jeff King
2008-04-30 17:24         ` [PATCH 2/3] bump rename limit defaults Jeff King
2008-04-30 17:25         ` [PATCH 3/3] diff: make "too many files" rename warning optional Jeff King
2008-05-03 17:34           ` Ramsay Jones
2008-05-04 19:23             ` Jeff King
2008-05-04 23:28               ` Paul Mackerras
2008-05-05 13:59                 ` Jeff King
2008-05-05 17:02                   ` Jeff King
2008-05-05 19:52                   ` Junio C Hamano
2008-05-12 11:15                     ` Paul Mackerras
2008-05-06 22:33                 ` Ramsay Jones
2008-05-06 22:29               ` Ramsay Jones
2008-05-04  0:10           ` Junio C Hamano
2008-05-04 19:20             ` 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=7viqxvta9h.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=akpm@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).