From: "Sverre Rabbelier" <srabbelier@gmail.com>
To: "Miklos Vajna" <vmiklos@frugalware.org>
Cc: git@vger.kernel.org, dsymonds@gmail.com
Subject: Re: [PATCH] A simple script to parse the results from the testcases
Date: Sun, 8 Jun 2008 02:56:09 +0200 [thread overview]
Message-ID: <bd6139dc0806071756k331c9b29obc5f1cb525ef47d8@mail.gmail.com> (raw)
In-Reply-To: <20080608004928.GG29404@genesis.frugalware.org>
On Sun, Jun 8, 2008 at 2:49 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Sun, Jun 08, 2008 at 02:34:25AM +0200, Sverre Rabbelier <srabbelier@gmail.com> wrote:
>> Awesome, what do you want to do with the other patches?
>
> Nothing? It's your series. :-)
Heh, I'm not sure what the protocol is here :P. I could send in the
series with your patch as second... that is, if I can figure out how
to apply it from gmail (maybe you can send me the patch as attachment?
:D).
>> I mean, this patch on it's own doesn't make a lot of sense, but with
>> [1/3] and [3/3] I think it deserves some proper reviewing by the list.
>
> Sure. I would suggest:
>
> 1) Remove that ugly /tmp/git-test-results, place it under t/.
I remember trying that but it not working, which was why I put it
there in the first place. I'll give it a shot again tomorrow though.
> 2) Resend a series indicating this is no longer a demonstration but a
> real series which you want to be included. ;-)
ACK on that one ;).
> Ah and it's bikesheding, but probably key_value_parser.sh is not the
> best name for such a script. Maybe aggregate-results.sh or something
> like that.
Sure, but that's what it was though, a simple key_value_parser, your
version is actually a result aggregator.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-06-08 0:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2008-05-12 9:33 ` [PATCH 2/3] A simple python script to parse the results from the testcases Sverre Rabbelier
2008-05-12 10:14 ` Jakub Narebski
2008-05-12 10:16 ` Sverre Rabbelier
2008-05-12 13:00 ` Johannes Schindelin
2008-05-12 13:05 ` Sverre Rabbelier
2008-05-12 13:24 ` Johannes Schindelin
2008-06-08 0:18 ` [PATCH] A simple " Miklos Vajna
2008-06-08 0:34 ` Sverre Rabbelier
2008-06-08 0:49 ` Miklos Vajna
2008-06-08 0:56 ` Sverre Rabbelier [this message]
2008-06-08 2:26 ` Miklos Vajna
2008-06-08 11:43 ` Sverre Rabbelier
2008-06-08 17:27 ` Johannes Schindelin
2008-06-08 17:30 ` Sverre Rabbelier
2008-06-08 18:06 ` Mikael Magnusson
2008-06-08 18:09 ` Sverre Rabbelier
2008-05-12 9:33 ` [PATCH 3/3] Hook up the result aggregation in the test makefile Sverre Rabbelier
2008-05-12 15:03 ` 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=bd6139dc0806071756k331c9b29obc5f1cb525ef47d8@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.org \
/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).