All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Eric Sunshine" <sunshine@sunshineco.com>,
	demerphq <demerphq@gmail.com>,
	"Torsten Bögershausen" <tboegi@web.de>,
	"Andreas Schwab" <schwab@linux-m68k.org>,
	newren@gmail.com, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: t6044 broken on pu
Date: Mon, 09 May 2016 11:36:09 -0700	[thread overview]
Message-ID: <xmqqh9e7ulie.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqr3dbulyp.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Mon, 09 May 2016 11:26:22 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Yes, I think the comment should just go.  Nobody used that alphabet
> form since it was written in d17cf5f3 (tests: Introduce test_seq,
> 2012-08-04).
>
>> I don't really care either way whether it is replaced or not (at one
>> point there were some people really interested in NO_PERL not even using
>> one-liners in the test suite, but I am not one of them).
>
> Neither am I, but I think it is prudent to drop that "letters".  The
> comment even says the letter form is not portable already, so the
> mention of GNU seq(1) is not helping at all.

-- >8 --
Subject: test-lib-functions.sh: remove misleading comment on test_seq

We never used the "letters" form since we came up with "test_seq" to
replace use of non-portable "seq" in our test script, which we
introduced it at d17cf5f3 (tests: Introduce test_seq, 2012-08-04).

We use this helper to either iterate for N times (i.e. the values on
the lines do not even matter), or just to get N distinct strings
(i.e. the values on the lines themselves do not really matter, but
we care that they are different from each other and reproducible).

Stop promising that we may allow using "letters"; this would open an
easier reimplementation that does not rely on $PERL, if somebody
later wants to.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 t/test-lib-functions.sh | 21 +++++++--------------
 1 file changed, 7 insertions(+), 14 deletions(-)

diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index 8d99eb3..cc9f61d 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -718,20 +718,13 @@ test_cmp_rev () {
 	test_cmp expect.rev actual.rev
 }
 
-# Print a sequence of numbers or letters in increasing order.  This is
-# similar to GNU seq(1), but the latter might not be available
-# everywhere (and does not do letters).  It may be used like:
-#
-#	for i in $(test_seq 100)
-#	do
-#		for j in $(test_seq 10 20)
-#		do
-#			for k in $(test_seq a z)
-#			do
-#				echo $i-$j-$k
-#			done
-#		done
-#	done
+# Print a sequence of integers in increasing order, either with
+# two arguments (start and end):
+#
+#     test_seq 1 5 -- outputs 1 2 3 4 5 one line at a time
+#
+# or with one argument (end), in which case it starts counting 
+# from 1.
 
 test_seq () {
 	case $# in

  reply	other threads:[~2016-05-09 18:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07 12:00 t6044 broken on pu Torsten Bögershausen
2016-05-07 12:19 ` Andreas Schwab
2016-05-07 13:15   ` Ramsay Jones
2016-05-07 13:43     ` Ramsay Jones
2016-05-07 16:18   ` Torsten Bögershausen
2016-05-08  2:21     ` Junio C Hamano
2016-05-08  6:54       ` Torsten Bögershausen
2016-05-08 18:20         ` Junio C Hamano
2016-05-09  4:43           ` Torsten Bögershausen
2016-05-09 18:22             ` Junio C Hamano
2016-05-09  6:30           ` demerphq
2016-05-09  8:33             ` Jeff King
2016-05-09 16:02               ` Eric Sunshine
2016-05-09 16:12                 ` Jeff King
2016-05-09 18:26                   ` Junio C Hamano
2016-05-09 18:36                     ` Junio C Hamano [this message]
2016-05-09 20:10                       ` Eric Sunshine
2016-05-09 21:08                       ` Junio C Hamano
2016-05-09 21:27                         ` Eric Sunshine
2016-05-10  2:41                       ` Jeff King

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=xmqqh9e7ulie.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=demerphq@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    --cc=schwab@linux-m68k.org \
    --cc=sunshine@sunshineco.com \
    --cc=tboegi@web.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.