From: Andrew Cagney <cagney@redhat.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk <frysk@sources.redhat.com>
Subject: Re: Automated build-and-test summary report (2007/05/23)
Date: Mon, 28 May 2007 19:35:00 -0000 [thread overview]
Message-ID: <465B262C.5090104@redhat.com> (raw)
In-Reply-To: <20070524192441.GC16276@ca-server1.us.oracle.com>
Kris,
Again, I would really appreciate it if we didn't fill the list with your
test-results. If the system must always post out its results then it
unfortunatly sounds like the best solution is to limit them to once a
week. Sigh.
Andrew
next prev parent reply other threads:[~2007-05-28 18:57 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 [this message]
2007-05-29 18:50 ` Andrew Cagney
2007-05-30 12:07 ` Kris Van Hees
2007-05-30 12:53 ` Mark Wielaard
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=465B262C.5090104@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sources.redhat.com \
--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).