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

[PATCH] pull: pull into void by fast-forwarding from empty tree

From
Thomas Rast <trast@inf.ethz.ch>
Date
Jun 20, 2013, 12:36 UTC
Message-ID
<45f6841746e5dcea03a97fc3ea24aef274728023.1371731513.git.trast@inf.ethz.ch>

The logic for pulling into an unborn branch was originally designed to be used on a newly-initialized repository (d09e79c, git-pull: allow pulling into an empty repository, 2006-11-16). It thus did not initially deal with uncommitted changes in the unborn branch. The case of an _unstaged_ untracked file was fixed by by 4b3ffe5 (pull: do not clobber untracked files on initial pull, 2011-03-25). However, it still clobbered existing staged files, both when the file exists in the merged commit (it will be overwritten), and when it does not (it will be lost!).

We fix this by doing a two-way merge, where the "current" side of the merge is an empty tree, and the "target" side is HEAD (already updated to FETCH_HEAD at this point). This amounts to claiming that all work in the index was done vs. an empty tree, and thus all content of the index is precious.

Reported-by: Stefan Schüßler <mail@stefanschuessler.de>
Signed-off-by: Thomas Rast <trast@inf.ethz.ch>
---
Stefan Schüßler <mail@stefanschuessler.de> writes:
> I think there's a bug in git pull. Doing a git pull in a fresh
> repository without any commits removes files in the index.
[...]
Thanks for the bug report!
 git-pull.sh     |  9 ++++++++-
 t/t5520-pull.sh | 24 ++++++++++++++++++++++++
 2 files changed, 32 insertions(+), 1 deletion(-)
diff --git a/git-pull.sh b/git-pull.sh
index 638aabb..1f84383 100755
--- a/git-pull.sh
+++ b/git-pull.sh
@@ -266,10 +266,17 @@ case "$merge_head" in
 	;;
 esac
 
+# Pulling into unborn branch: a shorthand for branching off
+# FETCH_HEAD, for lazy typers.
 if test -z "$orig_head"
 then
 	git update-ref -m "initial pull" HEAD $merge_head "$curr_head" &&
-	git read-tree -m -u HEAD || exit 1
+	# Two-way merge: we claim the index is based on an empty tree,
+	# and try to fast-forward to HEAD.  This ensures we will not
+	# lose index/worktree changes that the user already made on
+	# the unborn branch.
+	empty_tree=4b825dc642cb6eb9a060e54bf8d69288fbee4904
+	git read-tree -m -u $empty_tree HEAD || exit 1
 	exit
 fi
 
diff --git a/t/t5520-pull.sh b/t/t5520-pull.sh
index 6af6c63..927903c 100755
--- a/t/t5520-pull.sh
+++ b/t/t5520-pull.sh
@@ -57,6 +57,30 @@ test_expect_success 'pulling into void does not overwrite untracked files' '
 	)
 '
 
+test_expect_success 'pulling into void does not overwrite staged files' '
+	git init cloned-staged-colliding &&
+	(
+		cd cloned-staged-colliding &&
+		echo "alternate content" >file &&
+		git add file &&
+		test_must_fail git pull .. master &&
+		echo "alternate content" >expect &&
+		test_cmp expect file
+	)
+'
+
+test_expect_success 'pulling into void does not remove new staged files' '
+	git init cloned-staged-new &&
+	(
+		cd cloned-staged-new &&
+		echo "new tracked file" >newfile &&
+		git add newfile &&
+		git pull .. master &&
+		echo "new tracked file" >expect &&
+		test_cmp expect newfile
+	)
+'
+
 test_expect_success 'test . as a remote' '
 
 	git branch copy master &&
-- 
1.8.3.1.664.gae9f72a
Next: Jeff King
Message 1 of 20 in “pull: pull into void by fast-forwarding from empty tree”
  1. pull: pull into void by fast-forwarding from empty treeThomas Rast, Jun 20, 2013
  2. Jeff KingJun 20, 2013
  3. pull: merge into unborn by fast-forwarding from empty treeThomas Rast, Jun 20, 2013
  4. Jeff KingJun 20, 2013
  5. Thomas RastJun 20, 2013
  6. Thomas RastJun 20, 2013
  7. Jeff KingJun 20, 2013
  8. Thomas RastJun 20, 2013
  9. Thomas RastJun 20, 2013
  10. Junio C HamanoJun 20, 2013
  11. Jeff KingJun 20, 2013
  12. Junio C HamanoJun 20, 2013
  13. Jeff KingJun 20, 2013
  14. Junio C HamanoJun 20, 2013
  15. Jeff KingJun 20, 2013
  16. 0/2 pull into unborn branch safety treeJeff King, Jun 20, 2013
  17. 1/2 pull: update unborn branch tip after indexJeff King, Jun 20, 2013
  18. 2/2 pull: merge into unborn by fast-forwarding from empty treeJeff King, Jun 20, 2013
  19. Junio C HamanoJun 20, 2013
  20. Ramkumar RamachandraJun 20, 2013

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.