From: Mark Wielaard <mark@klomp.org>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: Andrew Cagney <cagney@redhat.com>, frysk@sourceware.org
Subject: Re: Automated build-and-test summary report (2007/05/23)
Date: Wed, 30 May 2007 12:53:00 -0000 [thread overview]
Message-ID: <1180526845.4441.17.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20070530011241.GB14523@ca-server1.us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On Tue, 2007-05-29 at 18:12 -0700, Kris Van Hees wrote:
> So, please enlighten me: what is the *real* problem here?
I like the test results and do always quickly look at them to see if
they correspond to what I am seeing locally. But I can see how it might
be annoying for them to appear on the main list. Lets create a
frysk-testresults@sourceware.org and encourage everybody to publish
their frysk test run results there. That way we have an easy way for
people to filter out the test runs from the main discussion list and
still keep an archive to consult for any historical issues which is
really valuable when some failure doesn't occur for someone locally, but
is visible on one of the test machines.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-30 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 15:04 Kris Van Hees
2007-05-23 21:47 ` Andrew Cagney
2007-05-24 7:50 ` Kris Van Hees
2007-05-24 19:25 ` Andrew Cagney
2007-05-24 20:39 ` Kris Van Hees
2007-05-28 19:35 ` Andrew Cagney
2007-05-29 18:50 ` Andrew Cagney
2007-05-30 12:07 ` Kris Van Hees
2007-05-30 12:53 ` Mark Wielaard [this message]
2007-05-30 21:10 ` Kris Van Hees
2007-06-01 15:27 ` Andrew Cagney
2007-05-30 13:31 ` Andrew Cagney
2007-05-30 16:08 ` Andrew Cagney
2007-05-31 8:17 ` Kris Van Hees
2007-05-31 18:05 ` Mark Wielaard
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=1180526845.4441.17.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=kris.van.hees@oracle.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).