From: Jakub Narebski <jnareb@gmail.com>
To: "Sverre Rabbelier" <sverre@rabbelier.nl>
Cc: "Git list" <git@vger.kernel.org>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH 1/3] Modified test-lib.sh to output stats to /tmp/git-test-results
Date: Sun, 08 Jun 2008 07:42:59 -0700 (PDT) [thread overview]
Message-ID: <m3tzg4vvgw.fsf@localhost.localdomain> (raw)
In-Reply-To: <1212933875-29947-1-git-send-email-sverre@rabbelier.nl>
"Sverre Rabbelier" <sverre@rabbelier.nl> writes:
> Because writing to the current directory is not possible, we write to /tmp/.
> Suggestions for a better location are welcome.
> + test_results_path="../test-results"
Errr... it looks like you forgot to update commit message.
But that aside, I quite like this series.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-06-08 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 14:04 [PATCH 1/3] Modified test-lib.sh to output stats to /tmp/git-test-results Sverre Rabbelier
2008-06-08 14:04 ` [PATCH 2/3] A simple script to parse the results from the testcases Sverre Rabbelier
2008-06-08 14:04 ` [PATCH 3/3] Hook up the result aggregation in the test makefile Sverre Rabbelier
2008-06-08 14:42 ` Jakub Narebski [this message]
2008-06-08 14:45 ` [PATCH 1/3] Modified test-lib.sh to output stats to /tmp/git-test-results Sverre Rabbelier
2008-06-08 18:53 ` Junio C Hamano
2008-06-08 19:02 ` Sverre Rabbelier
2008-06-08 20:59 ` Junio C Hamano
2008-06-09 0:44 ` [PATCH 4/4] Make test-lib warn if the directory changes Sverre Rabbelier
-- strict thread matches above, loose matches on Subject: below --
2008-05-12 9:33 [PATCH 0/3] Aggregate testcase results Sverre Rabbelier
2008-05-12 9:33 ` [PATCH 1/3] Modified test-lib.sh to output stats to /tmp/git-test-results Sverre Rabbelier
2008-05-12 14:55 ` Vegard Nossum
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=m3tzg4vvgw.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
--cc=sverre@rabbelier.nl \
/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).