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

Re: [PATCH] submodules: ensure clean environment when operating in a submodule

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 22, 2010, 23:16 UTC
Message-ID
<7vsk8s274t.fsf@alter.siamese.dyndns.org>
In-Reply-To
<cb7bb73a1002221456q6c113675i7453e0115814c99c@mail.gmail.com>
Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:
> Good point. All GIT_* env variables should be resent when descending
> into a submodule. Is there a way to loop over them, or do I have to do
> something horrible like env | grep ^GIT_ | cut -f1 -d=  to get the
> list?

I would suggest to enumerate only what you care about explicitly, without consulting the user's environment. The user may have variables you do not know about and not related to git at all.

IOW, don't try to be too clever for your own good ;-)
Previous: Giuseppe BilottaNext: Giuseppe Bilotta
Message 4 of 15 in “submodules: ensure clean environment when operating in a submodule”
  1. submodules: ensure clean environment when operating in a submoduleGiuseppe Bilotta, Feb 22, 2010
  2. Junio C HamanoFeb 22, 2010
  3. Giuseppe BilottaFeb 22, 2010
  4. Junio C HamanoFeb 22, 2010
  5. 1/2 shell setup: clear_local_git_env() functionGiuseppe Bilotta, Feb 22, 2010
  6. Johannes SixtFeb 23, 2010
  7. Giuseppe BilottaFeb 23, 2010
  8. 0/2 clear environment for submodulesGiuseppe Bilotta, Feb 23, 2010
  9. 1/2 shell setup: clear_local_git_env() functionGiuseppe Bilotta, Feb 23, 2010
  10. Jens LehmannFeb 23, 2010
  11. 2/2 submodules: ensure clean environment when operating in a submoduleGiuseppe Bilotta, Feb 23, 2010
  12. 2/2 submodules: ensure clean environment when operating in a submoduleGiuseppe Bilotta, Feb 22, 2010
  13. Johannes SchindelinFeb 23, 2010
  14. Heiko VoigtFeb 23, 2010
  15. Johannes SchindelinFeb 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.