Browse Source

t/README: correct an exception when breaking a && chain in tests

The correct advice should have been taken from c289c31 (t/t7006: ignore
return status of shell's unset builtin, 2010-06-02).  A real-life issue
we experienced was with "unset", not with "export" (exporting an
unset variable may have similar portability issues, though).

Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Jonathan Nieder 15 years ago committed by Junio C Hamano
parent
commit
bdcaa325b4
  1. 8
      t/README

8
t/README

@ -259,11 +259,11 @@ Do: @@ -259,11 +259,11 @@ Do:
test ...

That way all of the commands in your tests will succeed or fail. If
you must ignore the return value of something (e.g. the return
value of export is unportable) it's best to indicate so explicitly
with a semicolon:
you must ignore the return value of something (e.g., the return
after unsetting a variable that was already unset is unportable) it's
best to indicate so explicitly with a semicolon:

export HLAGH;
unset HLAGH;
git merge hla &&
git push gh &&
test ...

Loading…
Cancel
Save