[PATCH 2/2] t9001: use older Getopt::Long boolean prefix '--no' rather than '--no-'
- From
Brandon Casey <casey@nrlssc.navy.mil>
- Date
- Dec 3, 2009, 17:52 UTC
- Message-ID
- <cQVSAldE71QbE653CpBd7h4xSyLF0IW0Sr3unEDh7mhF8GHwF9Yy4OITTeQ_lmvCLmR9qnBq9a8@cipher.nrlssc.navy.mil>
- In-Reply-To
- <cQVSAldE71QbE653CpBd7qjd43g8URlxW7WO99KN4T0njgcXAbpAJQhTbfLeU5wxWrW84lsFVZE@cipher.nrlssc.navy.mil>
From: Brandon Casey <drafnel@gmail.com>
The '--no-chain-reply-to' option is a Getopt::Long boolean option. The '--no-' prefix (as in --no-chain-reply-to) for boolean options is not supported in Getopt::Long version 2.32 which was released with Perl 5.8.0. This version only supports '--no' as in '--nochain-reply-to'. More recent versions of Getopt::Long, such as version 2.34, support either prefix. So use the older form in the tests.
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil> --- t/t9001-send-email.sh | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/t/t9001-send-email.sh b/t/t9001-send-email.sh index fb51ab3..752adaa 100755 --- a/t/t9001-send-email.sh +++ b/t/t9001-send-email.sh @@ -827,7 +827,7 @@ test_expect_success 'no warning with an explicit --no-chain-reply-to' ' --dry-run \ --from="Example <nobody@example.com>" \ --to=nobody@example.com \ - --no-chain-reply-to \ + --nochain-reply-to \ outdir/000?-*.patch 2>errors >out && ! grep "no-chain-reply-to" errors '
-- 1.6.5.3