From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2015, #02; Tue, 14)
Date: Wed, 15 Apr 2015 10:32:17 +0200 [thread overview]
Message-ID: <552E2211.7080704@web.de> (raw)
In-Reply-To: <xmqqh9si1itr.fsf@gitster.dls.corp.google.com>
On 2015-04-14 23.49, Junio C Hamano wrote:
> * tg/perf-lib-test-perf-cleanup (2013-09-19) 2 commits
> - perf-lib: add test_perf_cleanup target
> - perf-lib: split starting the test from the execution
>
> Add test_perf_cleanup shell function to the perf suite, that allows
> the script writers to define a test with a clean-up action.
>
> Will hold.
Is there a chance to squeeze in a fix for this:
./t/perf/perf-lib.sh:185: error: echo -n is not portable (please use printf): echo -n " c$i"
next prev parent reply other threads:[~2015-04-15 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 21:49 What's cooking in git.git (Apr 2015, #02; Tue, 14) Junio C Hamano
2015-04-15 8:21 ` Johannes Schindelin
2015-04-15 8:32 ` Torsten Bögershausen [this message]
2015-04-15 18:26 ` Junio C Hamano
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=552E2211.7080704@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).