Re: [PATCH] Add ability to specify environment extension to run_command
- From
Shawn O. Pearce <spearce@spearce.org>
- Date
- May 22, 2007, 06:38 UTC
- Message-ID
- <20070522063821.GE11636@spearce.org>
- In-Reply-To
- <7v646l9xkn.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 14 quoted lines
> Martin Waitz <tali@admingilde.org> writes: > > > On Mon, May 21, 2007 at 04:02:42PM -0700, Junio C Hamano wrote: > >> I had a feeling that some callers needed to be able to unsetenv > >> some. How would this patch help them, or are they outside of > >> the scope? > > > > At first I had the same objection but the putenv documentation > > told me that at least in glibc you can unsetenv by providing > > the variable name without a "=". > > I recall SysV putenv() does not remove "ENVNAME" without '=', and > http://www.opengroup.org/onlinepubs/000095399/functions/putenv.html > seems to say that as well.
Are we overbuilding this thing?
I thought this thread all started because we wanted to run a command in a subproject, and did not want the parent's GIT_* environment variables to confuse the subproject process when it started. That's a pretty simple concept: clear any GIT_* environment variable that can change behavior in the subproject. And almost everyone who is trying to use this API and alter the env wants exactly that - a subproject command.
-- Shawn.