From: "Eli Zaretskii" <eliz@gnu.org>
To: Peter Barada <peter@the-baradas.com>
Cc: me@cgf.cx, gdb@sources.redhat.com
Subject: Re: [maint] [maint] Michael Chastain for testsuite
Date: Sat, 05 Jun 2004 10:09:00 -0000 [thread overview]
Message-ID: <8011-Sat05Jun2004130223+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040605001706.EB1B898C8A@baradas.org> (message from Peter Barada on Fri, 4 Jun 2004 20:17:06 -0400 (EDT))
> 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.
next prev parent reply other threads:[~2004-06-05 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 23:37 Michael Elizabeth Chastain
2004-06-04 23:57 ` Christopher Faylor
2004-06-05 0:17 ` Peter Barada
2004-06-05 10:09 ` Eli Zaretskii [this message]
2004-06-05 13:48 ` Bob Rossi
-- strict thread matches above, loose matches on Subject: below --
2004-06-05 2:12 Michael Elizabeth Chastain
2004-06-05 2:10 Michael Elizabeth Chastain
2004-06-04 19:52 Andrew Cagney
2004-06-04 20:13 ` Christopher Faylor
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=8011-Sat05Jun2004130223+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=me@cgf.cx \
--cc=peter@the-baradas.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