From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] is_submodule_modified(): clear environment properly
Date: Tue, 23 Feb 2010 23:13:36 +0100 [thread overview]
Message-ID: <cb7bb73a1002231413n3a38e344hce8188671763c17b@mail.gmail.com> (raw)
In-Reply-To: <4B844D07.8070406@web.de>
On Tue, Feb 23, 2010 at 10:47 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> Only GIT_INDEX_FILE was cleared until now, but other environment variables
> have to be cleared too before running git status in a submodule.
>
> And while at it, don't allocate a new strbuf for GIT_INDEX_FILE but use
> a string constant instead.
>
> Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
> ---
>
>
> I think it makes sense to clear the same environment variables here
> as Giuseppe Bilotta's patch did for the git shell commands, even
> though i am not aware of any bug reports yet.
I think this makes sense. This would be the third user of the "list of
repo-local vars", together with the shell function and the connect.c
code highlighted elsewhere, so I believe this really puts some more
pressure on a refactoring of the list generation. Maybe a static array
exportable via git-rev-parse?
Of course this third use-case has a difference in that GIT_DIR is
actually set to something else and not just cleared, but this
particular case could just deep-copy the array modifying the
appropriate entry.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2010-02-23 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 21:47 [PATCH] is_submodule_modified(): clear environment properly Jens Lehmann
2010-02-23 22:13 ` Giuseppe Bilotta [this message]
2010-02-24 3:32 ` Junio C Hamano
2010-02-24 6:43 ` Giuseppe Bilotta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cb7bb73a1002231413n3a38e344hce8188671763c17b@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).