From: Adam Butcher <dev.lists@jessamine.co.uk>
To: git@vger.kernel.org
Subject: Re: [PATCH] tests: Introduce test_seq
Date: Sat, 4 Aug 2012 22:10:08 +0000 (UTC) [thread overview]
Message-ID: <loom.20120805T000957-218@post.gmane.org> (raw)
In-Reply-To: 20120804101403.10ad79b5@gmail.com
Michał Kiedrowicz <michal.kiedrowicz <at> gmail.com> writes:
> Junio C Hamano <gitster <at> pobox.com> wrote:
> > diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
> > index c8b4ae3..7dc70eb 100644
> > --- a/t/test-lib-functions.sh
> > +++ b/t/test-lib-functions.sh
> > @@ -543,11 +543,12 @@ test_cmp() {
> > # done
> >
> > test_seq () {
> > - test $# = 2 && { first=$1; shift; } || first=1
> > - test $# = 1 ||
> > - error "bug in the test script: not 1 or 2 parameters to test_seq"
> > - last=$1
> > - "$PERL_PATH" -le 'print for "$ARGV[0]".."$ARGV[1]"' "$first" "$last"
> > + case $# in
> > + 1) set 1 "$@" ;;
> > + 2) ;;
> > + *) error "bug in the test script: not 1 or 2 parameters to
test_seq" ;;
> > + esac
> > + "$PERL_PATH" -le 'print for $ARGV[0]..$ARGV[1]' "$@"
> > }
> >
> > # This function can be used to schedule some commands to be run
-- >8 --
Subject: [PATCH] Fixup test_seq: ensure arguments passed to script.
If the arguments passed to to test_seq start with '-' (e.g. negative
integers) they are considered perl options and the program errors. By
prefixing the user argument list with '--' when passing to perl, this
is avoid and sequences involving negative numbers are possible.
---
t/test-lib-functions.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index 5a1a95a..ed44f5e 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -539,7 +539,7 @@ test_seq () {
2) ;;
*) error "bug in the test script: not 1 or 2 parameters to
test_seq" ;;
esac
- "$PERL_PATH" -le 'print for $ARGV[0]..$ARGV[1]' "$@"
+ "$PERL_PATH" -le 'print for $ARGV[0]..$ARGV[1]' -- "$@"
}
# This function can be used to schedule some commands to be run
--
1.7.11.msysgit.1.1.gf0affa1
next prev parent reply other threads:[~2012-08-04 22:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 21:11 [PATCH] Fix 'No newline...' annotation in rewrite diffs Adam Butcher
2012-08-02 21:33 ` Jeff King
2012-08-02 21:52 ` Junio C Hamano
2012-08-02 22:14 ` Jeff King
2012-08-03 7:49 ` Michał Kiedrowicz
2012-08-03 16:02 ` Jeff King
2012-08-03 16:46 ` Junio C Hamano
2012-08-03 17:00 ` Jeff King
2012-08-03 19:57 ` [PATCH] tests: Introduce test_seq Michał Kiedrowicz
2012-08-03 20:02 ` Jeff King
2012-08-03 20:53 ` Junio C Hamano
2012-08-03 22:02 ` Jeff King
2012-08-03 22:09 ` Michał Kiedrowicz
2012-08-04 16:38 ` Johannes Sixt
2012-08-04 23:05 ` Junio C Hamano
2012-08-06 17:52 ` Michał Kiedrowicz
2012-08-06 20:16 ` Jeff King
2012-08-03 22:21 ` Michał Kiedrowicz
2012-08-03 22:48 ` Junio C Hamano
2012-08-03 23:08 ` Jeff King
2012-08-03 23:12 ` Junio C Hamano
2012-08-04 8:14 ` Michał Kiedrowicz
2012-08-04 22:10 ` Adam Butcher [this message]
2012-08-03 20:04 ` Michał Kiedrowicz
2012-08-03 20:07 ` Jeff King
2012-08-03 20:12 ` Michał Kiedrowicz
2012-08-03 20:38 ` Michał Kiedrowicz
2012-08-03 20:41 ` Jeff King
2012-08-02 22:22 ` [PATCH] Fix 'No newline...' annotation in rewrite diffs Adam Butcher
2012-08-02 22:00 ` Junio C Hamano
2012-08-02 22:58 ` Adam Butcher
2012-08-04 21:07 ` Adam Butcher
2012-08-05 1:26 ` Junio C Hamano
2012-08-05 7:06 ` [PATCH] Fix '\ No " Adam Butcher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120805T000957-218@post.gmane.org \
--to=dev.lists@jessamine.co.uk \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).