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

[PATCH 2/2] git-stash apply --index: optimize postprocessing

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 28, 2007, 07:02 UTC
Message-ID
<7vy7h1t3hs.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<7vbqdxui72.fsf@assigned-by-dhcp.cox.net>

Originally, "apply --index" codepath was bolted on to the "update working tree files and index, but then revert the changes we make to the index except for added files so that we do not forget about them" codepath, almost as an afterthought. Because "apply --index" first prepares the final index state upfront, "revert except the added paths" postprocessing does not have to be done.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 git-stash.sh |   13 +++++++------
 1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/git-stash.sh b/git-stash.sh
index 873e7be..30425ce 100755
--- a/git-stash.sh
+++ b/git-stash.sh
@@ -157,15 +157,16 @@ apply_stash () {
 	if git-merge-recursive $b_tree -- $c_tree $w_tree
 	then
 		# No conflict
-		a="$TMP-added" &&
-		git diff --cached --name-only --diff-filter=A $c_tree >"$a" &&
-		git read-tree --reset $c_tree &&
-		git update-index --add --stdin <"$a" ||
-			die "Cannot unstage modified files"
-		rm -f "$a"
 		if test -n "$unstashed_index_tree"
 		then
 			git read-tree "$unstashed_index_tree"
+		else
+			a="$TMP-added" &&
+			git diff --cached --name-only --diff-filter=A $c_tree >"$a" &&
+			git read-tree --reset $c_tree &&
+			git update-index --add --stdin <"$a" ||
+				die "Cannot unstage modified files"
+			rm -f "$a"
 		fi
 		git status || :
 	else
-- 
1.5.3.rc3.16.g9f04-dirty
Previous: Junio C HamanoNext: しらいしななこ
Message 3 of 4 in “git-stash last-minute fixes”
  1. 0/2 git-stash last-minute fixesJunio C Hamano, Jul 28, 2007
  2. 1/2 Fix git-stash apply --indexJunio C Hamano, Jul 28, 2007
  3. 2/2 git-stash apply --index: optimize postprocessingJunio C Hamano, Jul 28, 2007
  4. しらいしななこJul 28, 2007

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.