aboutsummaryrefslogtreecommitdiff
path: root/merge-recursive.c
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2010-08-05 06:24:58 -0500
committerJunio C Hamano <gitster@pobox.com>2010-08-06 09:20:01 -0700
commit18b037a5b61532cba7f19efdb2e75c258d87d3d7 (patch)
treec41f8c974a9728d7ab8ce495a4527e121240664c /merge-recursive.c
parent73cf7f713da4fc797e2393a9e490ad4ec9466c53 (diff)
downloadgit-18b037a5b61532cba7f19efdb2e75c258d87d3d7.tar.gz
git-18b037a5b61532cba7f19efdb2e75c258d87d3d7.tar.xz
ll-merge: let caller decide whether to renormalize
Add a “renormalize” bit to the ll-merge options word so callers can decide on a case-by-case basis whether the merge is likely to have overlapped with a change in smudge/clean rules. This reveals a few commands that have not been taking that situation into account, though it does not fix them. No functional change intended. Cc: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com> Improved-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'merge-recursive.c')
-rw-r--r--merge-recursive.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/merge-recursive.c b/merge-recursive.c
index c0c9f0ccc..23f7a4d13 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -648,6 +648,7 @@ static int merge_3way(struct merge_options *o,
merge_status = ll_merge(result_buf, a->path, &orig, base_name,
&src1, name1, &src2, name2,
((o->call_depth ? LL_OPT_VIRTUAL_ANCESTOR : 0) |
+ (o->renormalize ? LL_OPT_RENORMALIZE : 0) |
create_ll_flag(favor)));
free(name1);