git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: reproducible unexpected behavior for 'git reset'

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 11, 2011, 22:41 UTC
Message-ID
<7voc10a1a2.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7vwrfoa3fg.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 6 quoted lines
>> I am able to reproduce a scenario where, after a 'commit' and a 'stash
>> pop' that results in a merge conflict, I need to 'reset' a file twice in
>> order to get the index back to HEAD.
>
> Thanks, you found a bug in "git reset [<commit>] -- path" codepath, it
> seems, when dealing with an unmerged path.

This patch is probably a wrong way to fix this issue; I have this suspicion that the original code for "reset [<commit>] -- paths..." codepath is correctly designed to deal with unmerged index, and it would probably need a deeper surgery.

-- >8 --
Subject: [PATCH] reset [<commit>] paths...: do not mishandle unmerged paths

By reading the index with unmerged content before running diff-index with the tree-ish we are reading from, read_from_tree() function ended up stuffing the object name from a wrong stage to the resulting index.

Noticed by John Nowak.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 builtin/reset.c  |    2 +-
 t/t7102-reset.sh |   15 +++++++++++++++
 2 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/builtin/reset.c b/builtin/reset.c
index 98bca04..09c8d2a 100644
--- a/builtin/reset.c
+++ b/builtin/reset.c
@@ -202,7 +202,7 @@ static int read_from_tree(const char *prefix, const char **argv,
 
 	index_fd = hold_locked_index(lock, 1);
 	index_was_discarded = 0;
-	read_cache();
+	read_cache_unmerged();
 	if (do_diff_cache(tree_sha1, &opt))
 		return 1;
 	diffcore_std(&opt);
diff --git a/t/t7102-reset.sh b/t/t7102-reset.sh
index f1cfc9a..1784412 100755
--- a/t/t7102-reset.sh
+++ b/t/t7102-reset.sh
@@ -429,6 +429,21 @@ test_expect_success '--mixed refreshes the index' '
 	test_i18ncmp expect output
 '
 
+test_expect_success 'resetting specific path that is unmerged' '
+	F1=$(git rev-parse HEAD:file1) &&
+	F2=$(git rev-parse HEAD:file2) &&
+	F3=$(git rev-parse HEAD:secondfile) &&
+	{
+		echo "000000 $_z40 0	file2" &&
+		echo "100644 $F1 1	file2" &&
+		echo "100644 $F2 2	file2" &&
+		echo "100644 $F3 3	file2"
+	} | git update-index --index-info &&
+	git ls-files -u &&
+	test_must_fail git reset HEAD file2 &&
+	git diff-index --exit-code --cached HEAD
+'
+
 test_expect_success 'disambiguation (1)' '
 
 	git reset --hard &&
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 9 in “reproducible unexpected behavior for 'git reset'”
  1. John NowakJul 10, 2011
  2. Junio C HamanoJul 11, 2011
  3. Junio C HamanoJul 11, 2011
  4. Junio C HamanoJul 14, 2011
  5. 0/2 refactoring diff-indexJunio C Hamano, Jul 19, 2011
  6. 1/2 diff-lib: simplify do_diff_cache()Junio C Hamano, Jul 19, 2011
  7. Jeff KingJul 19, 2011
  8. Junio C HamanoJul 19, 2011
  9. 2/2 diff-lib: refactor run_diff_index() and do_diff_cache()Junio C Hamano, Jul 19, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.