Merge branch 'jc/test-yes-doc'
Test doc update. * jc/test-yes-doc: test: caution on our version of 'yes'
This commit is contained in:
9
t/README
9
t/README
@ -932,6 +932,15 @@ library for your script to use.
|
|||||||
test_oid_init or test_oid_cache. Providing an unknown key is an
|
test_oid_init or test_oid_cache. Providing an unknown key is an
|
||||||
error.
|
error.
|
||||||
|
|
||||||
|
- yes [<string>]
|
||||||
|
|
||||||
|
This is often seen in modern UNIX but some platforms lack it, so
|
||||||
|
the test harness overrides the platform implementation with a
|
||||||
|
more limited one. Use this only when feeding a handful lines of
|
||||||
|
output to the downstream---unlike the real version, it generates
|
||||||
|
only up to 99 lines.
|
||||||
|
|
||||||
|
|
||||||
Prerequisites
|
Prerequisites
|
||||||
-------------
|
-------------
|
||||||
|
|
||||||
|
@ -1327,7 +1327,11 @@ then
|
|||||||
fi
|
fi
|
||||||
fi
|
fi
|
||||||
|
|
||||||
# Provide an implementation of the 'yes' utility
|
# Provide an implementation of the 'yes' utility; the upper bound
|
||||||
|
# limit is there to help Windows that cannot stop this loop from
|
||||||
|
# wasting cycles when the downstream stops reading, so do not be
|
||||||
|
# tempted to turn it into an infinite loop. cf. 6129c930 ("test-lib:
|
||||||
|
# limit the output of the yes utility", 2016-02-02)
|
||||||
yes () {
|
yes () {
|
||||||
if test $# = 0
|
if test $# = 0
|
||||||
then
|
then
|
||||||
|
Reference in New Issue
Block a user