public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk@sourceware.org
Subject: Re: Automated build-and-test summary report (2007/11/05)
Date: Tue, 06 Nov 2007 15:03:00 -0000	[thread overview]
Message-ID: <1194361421.3855.62.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20071106134446.GE10486@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

Hi Kris,

Thanks for that explanation. Much clearer now!

On Tue, 2007-11-06 at 08:44 -0500, Kris Van Hees wrote:
> Would it be more clear if I changed that to be:
> 
> 	First failure:  test (previously: no changes - not built)

Yes, adding previously is much better.
But maybe just put it on its own line?

  First failure this run     : test
  First failure previous run : no changes - not built

(It would be nice to have an entry also for the last time built and
where it failed that time.)

I think the real confusion comes from the "-".
Why not replace it with "so" (no changes so not built).
Or just spell it out completely "not built because no sources changed"
to be completely clear.

All the above is clearly nitpicking though. Now that I have read your
explanation I can easily parse any of the outputs.

Cheers,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2007-11-06 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071105140036.GA2015@oracle.com>
2007-11-06 10:25 ` Mark Wielaard
2007-11-06 11:42   ` Kris Van Hees
2007-11-06 12:23     ` Mark Wielaard
2007-11-06 13:45       ` Kris Van Hees
2007-11-06 15:03         ` Mark Wielaard [this message]

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=1194361421.3855.62.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --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).