All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Anders Melchiorsen" <mail@cup.kalibalik.dk>,
	git@vger.kernel.org, "Samuel Tardieu" <sam@rfc1149.net>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Junio C Hamano" <gitster@pobox.com>,
	"SZEDER Gábor" <szeder@ira.uka.de>
Subject: [PATCH] Fix for a merge where a branch has an F->D transition
Date: Mon, 11 May 2009 21:25:36 +0200	[thread overview]
Message-ID: <20090511192536.GA1485@blimp.localdomain> (raw)
In-Reply-To: <81b0412b0905110242u3624f0eeyc0dc9b2b987bfa2b@mail.gmail.com>

Some path names which transitioned from file to a directory were not
updated in the final part of the merge (loop around unmerged entries in
merge_trees), because the branch in process_renames which filtered out
updates for the files with the same content ("merged same as existing")
has left the rename entry in processed state. In this case, the
processing cannot be finished at the process_renames phase (because
the old file still blocks creation of directory where new files should
appear), and must be postponed until the update_entry phase.

Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
---

Alex Riesen, Mon, May 11, 2009 11:42:17 +0200:
> The problem is that if a file was replaced with a directory containing
> another file with the same content and mode, an attempt to merge it
> with a branch descended from a commit before this F->D transition will
> cause merge-recursive to break. It breaks even if there were no
> conflicting changes on that other branch.
> 
> 2009/5/11 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> >
> > Maybe you can turn this into a patch adding a test (with
> > test_expect_failure to mark it as a bug)?  This would make debugging a lot
> > easier, as a non-installed Git could be tested.
> 
> Here.
> 
>  t/t6020-merge-df.sh |   23 +++++++++++++++++++++++
>  1 files changed, 23 insertions(+), 0 deletions(-)
> 

Frankly, I'm not really sure. The solution came largely ... empirical
way. IOW, I tried more or less random things which looked like they
should fix the problem. So a review is very much appreciated. Please.

 merge-recursive.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/merge-recursive.c b/merge-recursive.c
index a3721ef..3c5420b 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -980,14 +980,15 @@ static int process_renames(struct merge_options *o,
 
 				if (mfi.clean &&
 				    sha_eq(mfi.sha, ren1->pair->two->sha1) &&
-				    mfi.mode == ren1->pair->two->mode)
+				    mfi.mode == ren1->pair->two->mode) {
 					/*
 					 * This messaged is part of
 					 * t6022 test. If you change
 					 * it update the test too.
 					 */
 					output(o, 3, "Skipped %s (merged same as existing)", ren1_dst);
-				else {
+					ren1->dst_entry->processed = 0;
+				} else {
 					if (mfi.merge || !mfi.clean)
 						output(o, 1, "Renaming %s => %s", ren1_src, ren1_dst);
 					if (mfi.merge)
-- 
1.6.3.28.ga852b

  reply	other threads:[~2009-05-11 19:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11  9:42 [PATCH] Add a reminder test case for a merge with F/D transition Alex Riesen
2009-05-11 19:25 ` Alex Riesen [this message]
2009-05-13  6:19   ` [PATCH] Fix for a merge where a branch has an F->D transition Junio C Hamano
2009-05-13  6:38     ` Alex Riesen
2009-05-13  9:59       ` Johannes Schindelin
2009-05-13 11:33         ` Alex Riesen
2009-05-20 10:34   ` Johannes Schindelin
2009-05-20 22:09     ` Alex Riesen

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=20090511192536.GA1485@blimp.localdomain \
    --to=raa.lkml@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mail@cup.kalibalik.dk \
    --cc=sam@rfc1149.net \
    --cc=szeder@ira.uka.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.