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>
Jonathan Nieder committed
Jul 20, 2010 at 19:01 UTC
bdcaa325b47fcacfecb781a28801aafc249ba288
1 file changed
+4
-4
t/README
+4
-4
@@ -259,11 +259,11 @@ Do:
259
test ...
260
261
That way all of the commands in your tests will succeed or fail. If
262
- you must ignore the return value of something (e.g. the return
263
- value of export is unportable) it's best to indicate so explicitly
264
- with a semicolon:
262
+ you must ignore the return value of something (e.g., the return
263
+ after unsetting a variable that was already unset is unportable) it's
264
+ best to indicate so explicitly with a semicolon:
265
266
- export HLAGH;
266
+ unset HLAGH;
267
git merge hla &&
268
git push gh &&
269
test ...