Re: [PATCH 2/2] bundle: use a strbuf to scan the log for boundary commits

From: Jeff King <peff@peff.net>
Date: Feb 22, 2012, 20:55 UTC
Message-ID: <20120222205500.GD6781@sigill.intra.peff.net>
In-Reply-To: <fa1553d59714fd89fdab1bf54af19ac631a30a8c.1329939233.git.trast@student.ethz.ch>

On Wed, Feb 22, 2012 at 08:34:23PM +0100, Thomas Rast wrote:

Show 9 quoted lines

> +# If "ridiculous" is at least 1004 chars, this traps a bug in old
> +# versions where the resulting 1025-char line (with --pretty=oneline)
> +# was longer than a 1024-char buffer
> +test_expect_success 'ridiculously long subject in boundary' '
> +
> +	: > file4 &&
> +	test_tick &&
> +	git add file4 &&
> +	printf "abcdefghijkl %s\n" $(seq 1 100) | git commit -F - &&

Seq is not portable. I usually use either

  perl -le "print for (1..100)"

or just do:

  z16=zzzzzzzzzzzzzzzz
  z256=$z16$z16$z16$z16$z16$z16$z16$z16
  z1024=$z256$z256$z256$z256$z256$z256$z256$z256

-Peff