From: "Torsten Bögershausen" <tboegi@web.de>
To: "Junio C Hamano" <gitster@pobox.com>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
newren@gmail.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: t6044 broken on pu
Date: Sun, 8 May 2016 08:54:06 +0200 [thread overview]
Message-ID: <5618208c-ce45-d65c-abf8-498cfe0f2f84@web.de> (raw)
In-Reply-To: <xmqqa8k11e8j.fsf@gitster.mtv.corp.google.com>
On 08.05.16 04:21, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>> That's true, but the test passes anyway.
> You can also remove the body of the test and replace it with "true"
> and say "the test passes anyway". Changing the test to use a file
> with only one line is irresponsible, if you do not know the nature
> of expected future bug that requires 10 lines to be there to
> manifest that the test wants to try.
>
> test_seq was invented exactly for the purpose of accomodating
> platforms that lack seq, so using it would probably be the best
> first step. Updating implementation of test_seq to avoid $PERL
> would be a separate step, if desired (I personally do not think
> that is worth it).
We don't need to invoke perl, when the shell can do that internally ?
May a simple
printf "1\n2\n3\n4\n5\n6\n7\n8\n9\n10\n"
be an option ?
next prev parent reply other threads:[~2016-05-08 6:54 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 [this message]
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
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=5618208c-ce45-d65c-abf8-498cfe0f2f84@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=schwab@linux-m68k.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).