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

[PATCH] require_work_tree: Look for top-level instead of is-inside-work-tree

From
Tor Arne Vestbø <tor.arne.vestbo@nokia.com>
Date
Jul 28, 2010, 16:47 UTC
Message-ID
<1280335624-90132-1-git-send-email-tor.arne.vestbo@nokia.com>

The documentation describes require_work_tree as guarding against bare repositories, and that's also the way it's used from porcelain such as git-rebase. When implemented using --is-inside-work-tree the samantics change, causing git-rebase to fail if run from outside GIT_WORK_TREE, even if GIT_WORK_TREE is valid.

Signed-off-by: Tor Arne Vestbø <tor.arne.vestbo@nokia.com>
---
 git-sh-setup.sh     |    2 +-
 t/t1501-worktree.sh |    9 +++++++++
 2 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/git-sh-setup.sh b/git-sh-setup.sh
index 6131670..f8e4428 100644
--- a/git-sh-setup.sh
+++ b/git-sh-setup.sh
@@ -141,7 +141,7 @@ cd_to_toplevel () {
 }
 
 require_work_tree () {
-	test "$(git rev-parse --is-inside-work-tree 2>/dev/null)" = true ||
+	test -n "$(git rev-parse --show-toplevel 2>/dev/null)" ||
 	die "fatal: $0 cannot be used without a working tree."
 }
 
diff --git a/t/t1501-worktree.sh b/t/t1501-worktree.sh
index bd8b607..45b09e7 100755
--- a/t/t1501-worktree.sh
+++ b/t/t1501-worktree.sh
@@ -114,6 +114,15 @@ test_expect_success 'repo finds its work tree from work tree, too' '
 	 test sub/dir/tracked = "$(git ls-files)")
 '
 
+test_expect_success 'require_work_tree finds work tree' '
+	(cd repo.git/work &&
+	. "$(git --exec-path)"/git-sh-setup &&
+	cd .. &&
+	require_work_tree &&
+	cd .. &&
+	require_work_tree)
+'
+
 test_expect_success '_gently() groks relative GIT_DIR & GIT_WORK_TREE' '
 	(cd repo.git/work/sub/dir &&
 	GIT_DIR=../../.. GIT_WORK_TREE=../.. GIT_PAGER= \
-- 
1.7.2.19.g48995
Next: Junio C Hamano
Message 1 of 6 in “require_work_tree: Look for top-level instead of is-inside-work-tree”
  1. require_work_tree: Look for top-level instead of is-inside-work-treeTor Arne Vestbø, Jul 28, 2010
  2. Junio C HamanoJul 28, 2010
  3. Tor Arne VestbøJul 30, 2010
  4. Michael J GruberAug 2, 2010
  5. Junio C HamanoAug 2, 2010
  6. Michael J GruberAug 3, 2010

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.