git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Heiko Voigt <hvoigt@hvoigt.net>
To: git@vger.kernel.org
Subject: [PATCH] fix read-tree storing wrong tree reference with modified index
Date: Fri, 9 Jul 2010 00:46:53 +0200	[thread overview]
Message-ID: <20100708224653.GB50404@book.hvoigt.net> (raw)

In 456156d a shortcut to priming the index tree reference was
introduced.

When read-tree is called with -m one would expect it to merge the
tree read and the existing one stored in the index. It did that
correctly but the index referenced the wrong tree. This sometimes lead
to a situation that the diff of

  index <-> HEAD       (git diff)
  index <-> worktree   (git diff --cached)

was empty but

  HEAD <-> worktree    (git diff HEAD)

did show changes because the SHA1 of the worktree files were still in
the index but the referenced tree came from HEAD. The test demonstrates
how to create such a situation.

Signed-off-by: Heiko Voigt <hvoigt@hvoigt.net>
---

I stumbled upon this bug when using git gui. For some reason it does not
always result in the situation described above. I am not sure whether
this is the correct fix or if we expect a different behavior from
read-tree. So another set of eyes is appreciated.

 builtin/read-tree.c         |    6 ++++--
 t/t1001-read-tree-m-2way.sh |   16 ++++++++++++++++
 2 files changed, 20 insertions(+), 2 deletions(-)

diff --git a/builtin/read-tree.c b/builtin/read-tree.c
index 8bdcab1..3cb6cdd 100644
--- a/builtin/read-tree.c
+++ b/builtin/read-tree.c
@@ -221,11 +221,13 @@ int cmd_read_tree(int argc, const char **argv, const char *unused_prefix)
 	 * what came from the tree.
 	 *
 	 * The same holds true if we are switching between two trees
-	 * using read-tree -m A B.  The index must match B after that.
+	 * using read-tree A B (without -m). The index must match B
+	 * after that. With given -m it can be a mix of the old index
+	 * and the read one.
 	 */
 	if (nr_trees == 1 && !opts.prefix)
 		prime_cache_tree(&active_cache_tree, trees[0]);
-	else if (nr_trees == 2 && opts.merge)
+	else if (nr_trees == 2 && !opts.merge)
 		prime_cache_tree(&active_cache_tree, trees[1]);
 
 	if (write_cache(newfd, active_cache, active_nr) ||
diff --git a/t/t1001-read-tree-m-2way.sh b/t/t1001-read-tree-m-2way.sh
index 6327d20..a5ad3c1 100755
--- a/t/t1001-read-tree-m-2way.sh
+++ b/t/t1001-read-tree-m-2way.sh
@@ -390,4 +390,20 @@ test_expect_success \
      git ls-files --stage | tee >treeMcheck.out &&
      test_cmp treeM.out treeMcheck.out'
 
+test_expect_success '-m references the correct modified tree' '
+	echo > file-a &&
+	echo > file-b &&
+	git add file-a file-b &&
+	git commit -a -m "test for correct modified tree"
+	git branch initial-mod &&
+	echo b > file-b &&
+	git commit -a -m "B" &&
+	echo a > file-a &&
+	git add file-a &&
+	git ls-tree $(git write-tree) file-a > expect &&
+	git read-tree -m HEAD initial-mod &&
+	git ls-tree $(git write-tree) file-a > actual &&
+	test_cmp expect actual
+'
+
 test_done
-- 
1.7.2.rc2.1.g8c934

             reply	other threads:[~2010-07-08 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 22:46 Heiko Voigt [this message]
2010-07-08 23:42 ` [PATCH] fix read-tree storing wrong tree reference with modified index Junio C Hamano
2010-07-09  0:45   ` Junio C Hamano
2010-07-09 10:04     ` Heiko Voigt

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100708224653.GB50404@book.hvoigt.net \
    --to=hvoigt@hvoigt.net \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).