From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: min, max and nans
Date: 07 Jun 2003 01:17:38 +0200 [thread overview]
Message-ID: <87r8666bjh.fsf@zagadka.ping.de> (raw)
In-Reply-To: <xy71xy7kxb9.fsf@nada.kth.se>
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
> In my opinion, the idea of sending build logs at failure (not when
> Guile compiles and tests OK) to guile-cvs@gnu.org is an excellent
> idea.
>
> If I have at any time been critical against it, it was because it is a
> good idea to start off with no build failures so that people feel
> motivated to fix things.
Hehe, yeah, I could totally understand your point (if I understood it
;-). For those interested: the snapshots were failing for over a week
due to problems in the build environment (I think). I didn't get
around to fix the build environment in a timely manner and so people
saw error logs that were not relevant to them. That could only teach
them to ignore these logs. So I stopped posting them automatically.
We _did_ start off with no build failures but that was hard to notice
since no logs are sent when there is no build failure.
I think it is also OK when just I myself watch the logs and contact
the people that I deem responsible for failures.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-06-06 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 23:26 min, max and nans Kevin Ryde
2003-05-17 20:02 ` Marius Vollmer
2003-05-30 0:20 ` Kevin Ryde
2003-06-04 16:08 ` Kevin Ryde
2003-06-05 12:48 ` Marius Vollmer
2003-06-06 16:03 ` Mikael Djurfeldt
2003-06-06 23:17 ` Marius Vollmer [this message]
2003-06-15 0:17 ` Kevin Ryde
2003-06-18 23:36 ` Marius Vollmer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r8666bjh.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).