From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-18199-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 22063 invoked by alias); 5 Jun 2004 10:09:21 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 22000 invoked from network); 5 Jun 2004 10:09:19 -0000
Received: from unknown (HELO aragorn.inter.net.il) (192.114.186.23)
  by sourceware.org with SMTP; 5 Jun 2004 10:09:19 -0000
Received: from zaretski (pns03-196-13.inter.net.il [80.230.196.13])
	by aragorn.inter.net.il (MOS 3.4.6-GR)
	with ESMTP id DAG74583;
	Sat, 5 Jun 2004 13:04:54 +0300 (IDT)
Date: Sat, 05 Jun 2004 10:09:00 -0000
From: "Eli Zaretskii" <eliz@gnu.org>
To: Peter Barada <peter@the-baradas.com>
Message-Id: <8011-Sat05Jun2004130223+0300-eliz@gnu.org>
CC: me@cgf.cx, gdb@sources.redhat.com
In-reply-to: <20040605001706.EB1B898C8A@baradas.org> (message from Peter
	Barada on Fri, 4 Jun 2004 20:17:06 -0400 (EDT))
Subject: Re: [maint] [maint] Michael Chastain for testsuite
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <20040604233726.4FA074B104@berman.michael-chastain.com> <20040604235736.GA3283@coe.casa.cgf.cx> <20040605001706.EB1B898C8A@baradas.org>
X-SW-Source: 2004-06/txt/msg00036.txt.bz2

> From: Peter Barada <peter@the-baradas.com>
> Date: Fri,  4 Jun 2004 20:17:06 -0400 (EDT)
> 
> I'd like to see a testcase being *required* to be added that shows a
> current failure *before* a patch for its fix is accepted.

That's a noble goal, but what do we do in cases where it's
impractical?  For example, a particular bug could only be raising its
ugly head in a very large program.