From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb@sources.redhat.com, me@cgf.cx
Subject: Re: [maint] [maint] Michael Chastain for testsuite
Date: Sat, 05 Jun 2004 02:10:00 -0000 [thread overview]
Message-ID: <20040605021032.154B94B104@berman.michael-chastain.com> (raw)
cgf> Does that translate into every bug reported eventually gets a test?
Hmmm, to put that in process terms: it means that a bug can't be closed
until there is a test for that bug in the test suite.
That would be good, but I'm not ready to go as far as to make it
a requirement for closing a PR. We've already got several problems
with PR's: the number of open PR's increases with time; and most PR's
go for a long time before getting any attention. I like to be a little
conservative about closing PR's but I'm not willing to add a requirement
that a PR has a test.
cgf> Would it make sense to add the test for a reported bug before a patch to
cgf> fix it is submitted?
I don't think so. It might be sensible to have these requirements
in parallel:
test must be committed before closing PR
code fix must be committed before closing PR
But I don't think it helps to require "test must be committed before
code fix is committed".
Michael C
next reply other threads:[~2004-06-05 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 2:10 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-05 2:12 Michael Elizabeth Chastain
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
2004-06-05 13:48 ` Bob Rossi
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=20040605021032.154B94B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=me@cgf.cx \
/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).