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

[PATCHv3 4/5] shell setup: clear_local_git_env() function

From
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date
Feb 23, 2010, 23:35 UTC
Message-ID
<1266968136-11129-5-git-send-email-giuseppe.bilotta@gmail.com>
In-Reply-To
<1266968136-11129-1-git-send-email-giuseppe.bilotta@gmail.com>

Introduce an auxiliary function to clear all repo-local environment variables. This should be invoked by any shell script that switches repository during execution, to ensure that the environment is clean and that things such as the git dir and worktree are set up correctly.

Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
---
 git-sh-setup.sh |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/git-sh-setup.sh b/git-sh-setup.sh
index 7a09566..6131670 100644
--- a/git-sh-setup.sh
+++ b/git-sh-setup.sh
@@ -172,6 +172,13 @@ get_author_ident_from_commit () {
 	LANG=C LC_ALL=C sed -ne "$pick_author_script"
 }
 
+# Clear repo-local GIT_* environment variables. Useful when switching to
+# another repository (e.g. when entering a submodule). See also the env
+# list in git_connect()
+clear_local_git_env() {
+	unset $(git rev-parse --local-env-vars)
+}
+
 # Make sure we are in a valid repository of a vintage we understand,
 # if we require to be in a git repository.
 if test -z "$NONGIT_OK"
-- 
1.7.0.200.g5ba36.dirty
Previous: Giuseppe BilottaNext: Giuseppe Bilotta
Message 7 of 8 in “[PATCHv3 0/5] repo-local env vars handling”
  1. Giuseppe BilottaFeb 23, 2010
  2. 1/5 cache: static list of repo-local env varsGiuseppe Bilotta, Feb 23, 2010
  3. 2/5 connect: use static list of repo-local env varsGiuseppe Bilotta, Feb 23, 2010
  4. Johannes SixtFeb 24, 2010
  5. Giuseppe BilottaFeb 24, 2010
  6. 3/5 rev-parse: --local-env-vars optionGiuseppe Bilotta, Feb 23, 2010
  7. 4/5 shell setup: clear_local_git_env() functionGiuseppe Bilotta, Feb 23, 2010
  8. 5/5 submodules: ensure clean environment when operating in a submoduleGiuseppe Bilotta, Feb 23, 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.