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

[PATCH 1/6] submodule foreach: correct path display in recursive submodules

From
Stefan Beller <sbeller@google.com>
Date
Mar 29, 2016, 23:02 UTC
Message-ID
<1459292558-5840-2-git-send-email-sbeller@google.com>
In-Reply-To
<1459292558-5840-1-git-send-email-sbeller@google.com>

The new test replicates the previous test with the difference of executing from a sub directory. By executing from a sub directory all we would expect all displayed paths to be prefixed by '../'.

Prior to this patch the test would report
    Entering 'nested1/nested2/../nested3'
instead of the expected
    Entering '../nested1/nested2/nested3'

because the prefix is put unconditionally in front and after that a computed display path with is affected by `wt_prefix`. This is wrong as any relative path computation would need to be at the front. By emptying the `wt_prefix` in recursive submodules and adding the information of any relative path into the `prefix` this is fixed.

Signed-off-by: Stefan Beller <sbeller@google.com>
---
 git-submodule.sh             |  3 ++-
 t/t7407-submodule-foreach.sh | 20 ++++++++++++++++++++
 2 files changed, 22 insertions(+), 1 deletion(-)
diff --git a/git-submodule.sh b/git-submodule.sh
index 43c68de..2838069 100755
--- a/git-submodule.sh
+++ b/git-submodule.sh
@@ -417,10 +417,11 @@ cmd_foreach()
 			say "$(eval_gettext "Entering '\$prefix\$displaypath'")"
 			name=$(git submodule--helper name "$sm_path")
 			(
-				prefix="$prefix$sm_path/"
+				prefix="$(relative_path $prefix$sm_path)/"
 				clear_local_git_env
 				cd "$sm_path" &&
 				sm_path=$(relative_path "$sm_path") &&
+				wt_prefix=
 				# we make $path available to scripts ...
 				path=$sm_path &&
 				if test $# -eq 1
diff --git a/t/t7407-submodule-foreach.sh b/t/t7407-submodule-foreach.sh
index 7ca10b8..776b349 100755
--- a/t/t7407-submodule-foreach.sh
+++ b/t/t7407-submodule-foreach.sh
@@ -178,6 +178,26 @@ test_expect_success 'test messages from "foreach --recursive"' '
 '
 
 cat > expect <<EOF
+Entering '../nested1'
+Entering '../nested1/nested2'
+Entering '../nested1/nested2/nested3'
+Entering '../nested1/nested2/nested3/submodule'
+Entering '../sub1'
+Entering '../sub2'
+Entering '../sub3'
+EOF
+
+test_expect_success 'test messages from "foreach --recursive" from subdirectory' '
+	(
+		cd clone2 &&
+		mkdir untracked &&
+		cd untracked &&
+		git submodule foreach --recursive >../../actual
+	) &&
+	test_i18ncmp expect actual
+'
+
+cat > expect <<EOF
 nested1-nested1
 nested2-nested2
 nested3-nested3
-- 
2.8.0.6.g3d0b0ba
Previous: Stefan BellerNext: Junio C Hamano
Message 2 of 12 in “[PATCHv3 0/6] Fix path bugs in submodule commands executed from sub dir”
  1. Stefan BellerMar 29, 2016
  2. 1/6 submodule foreach: correct path display in recursive submodulesStefan Beller, Mar 29, 2016
  3. Junio C HamanoMar 29, 2016
  4. 2/6 submodule update --init: correct path handling in recursive submodulesStefan Beller, Mar 29, 2016
  5. Junio C HamanoMar 29, 2016
  6. Stefan BellerMar 30, 2016
  7. 3/6 submodule status: correct path handling in recursive submodulesStefan Beller, Mar 29, 2016
  8. Junio C HamanoMar 29, 2016
  9. 4/6 submodule update: align reporting path for custom command executionStefan Beller, Mar 29, 2016
  10. Junio C HamanoMar 29, 2016
  11. 5/6 submodule update: test recursive path reporting from subdirectoryStefan Beller, Mar 29, 2016
  12. 6/6 t7407: make expectation as clear as possibleStefan Beller, Mar 29, 2016

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.