From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: "Andreas Schwab" <schwab@linux-m68k.org>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: newren@gmail.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: t6044 broken on pu
Date: Sat, 7 May 2016 14:43:51 +0100 [thread overview]
Message-ID: <572DF117.8060400@ramsayjones.plus.com> (raw)
In-Reply-To: <572DEA81.4050605@ramsayjones.plus.com>
On 07/05/16 14:15, Ramsay Jones wrote:
>
>
> On 07/05/16 13:19, Andreas Schwab wrote:
>> Torsten Bögershausen <tboegi@web.de> writes:
>>
>>> The "seq" is not understood by all shells,
>>> using printf fixes this,
>>>
>>> index 20a3ffe..48d964e 100755
>>> --- a/t/t6044-merge-unrelated-index-changes.sh
>>> +++ b/t/t6044-merge-unrelated-index-changes.sh
>>> @@ -20,7 +20,7 @@ test_description="merges with unrelated index changes"
>>> # Commit E: renames a->subdir/a, adds subdir/e
>>>
>>> test_expect_success 'setup trivial merges' '
>>> - seq 1 10 >a &&
>>> + printf 1 2 3 4 5 7 8 9 10 >a &&
>>
>> $ printf 1 2 3 4 5 7 8 9 10
>> 1
>
> yep, I think:
>
> printf "%d\n" 1 2 3 4 5 6 7 8 9 10 >a &&
>
> would be equivalent.
>
Having said that, there is also 'test_seq' which you can use
to avoid portability problems (although it uses perl, so could
be viewed as a bit heavyweight):
test_seq 1 10 >a &&
ATB,
Ramsay Jones
next prev parent reply other threads:[~2016-05-07 13:43 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 [this message]
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
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=572DF117.8060400@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=schwab@linux-m68k.org \
--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 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).