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

Re: [PATCH] Fix wrong failures in config test

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 10, 2011, 17:29 UTC
Message-ID
<20110110172931.GB7882@burratino>
In-Reply-To
<4d2b3ecd.7c62abb5.bm000@wupperonline.de>
Ingo Brückl wrote:
> Jonathan Nieder wrote on Mon, 10 Jan 2011 10:52:51 -0600:
Show 6 quoted lines
>> How does output from "sh t1300-repo-config.sh -v -i" end?
>
>   expecting success: git config --rename-section branch.eins branch.zwei
>   fatal: No such section!
>   not ok - 50 rename section
>   #       git config --rename-section branch.eins branch.zwei
Thanks.
> The problem is that the last 'git config' worked on other-config due to
> variable GIT_CONFIG.
I'm still missing something.
	GIT_CONFIG=other-config git config -l > output
	echo $GIT_CONFIG

should result in no output to stdout, right? In other words, the construct

	envvar=value git command
is not supposed to pollute the current environment.

It sounds like you've checked that "unset GIT_CONFIG" fixes it; what's left is to explain why GIT_CONFIG had a value in the first place.

Confused, Jonathan

Previous: Ingo Br ücklNext: Junio C Hamano
Message 4 of 11 in “Fix wrong failures in config test”
  1. Fix wrong failures in config testIngo Br ückl, Jan 10, 2011
  2. Jonathan NiederJan 10, 2011
  3. Ingo Br ücklJan 10, 2011
  4. Jonathan NiederJan 10, 2011
  5. Junio C HamanoJan 10, 2011
  6. Ingo Br ücklJan 10, 2011
  7. Jonathan NiederJan 10, 2011
  8. Junio C HamanoJan 10, 2011
  9. Jonathan NiederJan 10, 2011
  10. Ingo Br ücklJan 10, 2011
  11. Jonathan NiederJan 10, 2011

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.