From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Tom G. Christensen" <tgc@jupiterrise.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Buildstat update for 4.3
Date: Sat, 28 Jun 2008 16:12:00 -0000 [thread overview]
Message-ID: <alpine.LSU.1.10.0806281753030.17007@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20080627204540.GA2214@ares.tgcnet>
On Fri, 27 Jun 2008, Tom G. Christensen wrote:
> I wrote some scripts to cross check the testresult archive against the
> buildstat page.
> They can assist in finding typos, misplaced links and missing results.
Very nice! Looking at the result, your script indeed caught/fixed a
number of issues.
Do you plan on providing this kind of input regularily going forward?
That would be a nice contribution.
> They're available on request for anyone interested.
I wonder whether we could ultimately achieve a state where your scripts
would come up with a patch completely on their own? After running them
in attended mode for a while, we could then even consider just putting
them into a cron job and having them send the results in parallel to
making changes directly.
Gerald
next prev parent reply other threads:[~2008-06-28 16:02 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 20:45 Tom G. Christensen
2008-06-28 16:12 ` Gerald Pfeifer [this message]
2008-06-28 21:43 ` Tom G. Christensen
2008-06-30 0:10 ` Gerald Pfeifer
2008-07-01 21:39 ` Janis Johnson
2008-07-23 10:19 Tom G. Christensen
2008-07-23 10:35 ` Gerald Pfeifer
2008-08-03 8:42 Tom G. Christensen
2008-08-09 23:18 ` Gerald Pfeifer
2008-09-03 18:41 Tom G. Christensen
2008-09-03 22:57 ` Janis Johnson
2008-09-04 16:12 ` Tom G. Christensen
2008-09-04 17:09 ` Janis Johnson
2008-09-04 18:39 ` Tom G. Christensen
2008-09-04 18:56 ` Janis Johnson
2008-09-15 19:21 Tom G. Christensen
2008-09-16 7:07 ` Gerald Pfeifer
2008-10-01 20:40 Tom G. Christensen
2008-10-01 22:05 ` Janis Johnson
2008-10-16 9:35 Tom G. Christensen
2008-10-16 16:03 ` Gerald Pfeifer
2008-11-05 20:30 Tom G. Christensen
2008-11-05 23:57 ` Janis Johnson
2008-11-16 14:20 Tom G. Christensen
2008-11-16 20:08 ` Gerald Pfeifer
2008-12-02 14:26 Tom G. Christensen
2008-12-15 20:48 Tom G. Christensen
2008-12-27 15:27 ` Gerald Pfeifer
2009-01-28 20:51 Tom G. Christensen
2009-01-28 21:51 Tom G. Christensen
2009-01-28 23:59 ` Janis Johnson
2009-02-06 9:04 Tom G. Christensen
2009-02-07 0:07 ` Janis Johnson
2009-03-16 15:43 Tom G. Christensen
2009-03-17 0:27 ` Gerald Pfeifer
2009-07-05 14:36 Tom G. Christensen
2009-07-06 18:30 ` Janis Johnson
2009-08-16 14:38 Tom G. Christensen
2009-08-16 22:15 ` Gerald Pfeifer
2009-09-26 12:22 Tom G. Christensen
2009-09-26 13:10 ` Gerald Pfeifer
2009-10-21 19:19 Tom G. Christensen
2009-10-22 0:39 ` Gerald Pfeifer
2009-12-04 15:36 Tom G. Christensen
2009-12-18 9:48 ` Gerald Pfeifer
2010-01-06 6:11 Tom G. Christensen
2010-01-06 10:12 ` Gerald Pfeifer
2010-06-01 19:45 Tom G. Christensen
2010-06-06 9:41 ` Gerald Pfeifer
2010-08-05 8:01 Tom G. Christensen
2010-08-07 11:53 ` Gerald Pfeifer
2010-09-01 19:37 Tom G. Christensen
2010-09-01 20:03 ` Gerald Pfeifer
2010-10-03 7:28 Tom G. Christensen
2010-10-07 1:53 ` Gerald Pfeifer
2011-06-03 7:48 Tom G. Christensen
2011-06-04 10:41 ` Gerald Pfeifer
2011-08-20 19:52 Tom G. Christensen
2011-08-21 11:21 ` Gerald Pfeifer
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=alpine.LSU.1.10.0806281753030.17007@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tgc@jupiterrise.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 read-only IMAP folder(s) and NNTP newsgroup(s).