From: Andreas Schwab <schwab@linux-m68k.org>
To: "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, 07 May 2016 14:19:47 +0200 [thread overview]
Message-ID: <878tzmrrfg.fsf@linux-m68k.org> (raw)
In-Reply-To: <7d747193-7ba1-e274-86dc-427ed0f124c9@web.de> ("Torsten Bögershausen"'s message of "Sat, 7 May 2016 14:00:08 +0200")
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
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-05-07 12:19 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 [this message]
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
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=878tzmrrfg.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=newren@gmail.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.