From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22461 invoked by alias); 31 May 2007 08:17:41 -0000 Received: (qmail 22453 invoked by uid 22791); 31 May 2007 08:17:40 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,FORGED_RCVD_HELO X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (83.160.170.119) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 31 May 2007 08:17:36 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.43) id 1Htfsl-0000pk-1p for frysk@sourceware.org; Thu, 31 May 2007 10:19:43 +0200 Subject: Re: Automated build-and-test summary report (2007/05/23) From: Mark Wielaard To: frysk@sourceware.org In-Reply-To: <20070530210915.GE30260@ca-server1.us.oracle.com> References: <20070523141034.GA16276@ca-server1.us.oracle.com> <46545CB3.6000509@redhat.com> <20070523214658.GB16276@ca-server1.us.oracle.com> <4655CCF6.8080607@redhat.com> <20070524192441.GC16276@ca-server1.us.oracle.com> <465B262C.5090104@redhat.com> <465C6197.6030405@redhat.com> <20070530011241.GB14523@ca-server1.us.oracle.com> <465D7CC2.9080603@redhat.com> <20070530210915.GE30260@ca-server1.us.oracle.com> Content-Type: text/plain Date: Thu, 31 May 2007 18:05:00 -0000 Message-Id: <1180599451.4561.7.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00226.txt.bz2 On Wed, 2007-05-30 at 14:09 -0700, Kris Van Hees wrote: > You and everyone on the team (past and present) deserve credit for the > work you do and have done. I never have and never will deny that. But > as a professional courtesy, I'd expect the same in return. To clarify. The fact that Kris could often test and confirm or deny failures and crashes happening on specific setups was a great way for me to know whether or not I was looking at a kernel issue or whether we had identified a bug in the frysk-core/state machine. Thanks Kris. Mark