summaryrefslogtreecommitdiff
path: root/builtin-count-objects.c
diff options
context:
space:
mode:
authorH.Merijn Brand <h.m.brand@xs4all.nl>2007-12-04 22:45:16 +0000
committerJunio C Hamano <gitster@pobox.com>2007-12-04 14:48:45 -0800
commit5188408057b31a604f00496582aa873054ad6746 (patch)
treee753db084f0eb5b31fc9c61a972dc4f9d20eb9d0 /builtin-count-objects.c
parente5d3de5c457d1a82c921b9bf2cd9a962970ce30e (diff)
downloadgit-5188408057b31a604f00496582aa873054ad6746.tar.gz
Do not rely on the exit status of "unset" for unset variables
POSIX says that exit status "0" means that "unset" successfully unset the variable. However, it is kind of ambiguous if an environment variable which was not set could be successfully unset. At least the default shell on HP-UX insists on reporting an error in such a case, so just ignore the exit status of "unset". [Dscho: extended the patch to git-submodule.sh, as Junio realized that this is the only other place where we check the exit status of "unset".] Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin-count-objects.c')
0 files changed, 0 insertions, 0 deletions