From: Christopher Faylor <me@cgf.cx>
To: gdb@sources.redhat.com
Subject: Re: [maint] [maint] Michael Chastain for testsuite
Date: Fri, 04 Jun 2004 23:57:00 -0000 [thread overview]
Message-ID: <20040604235736.GA3283@coe.casa.cgf.cx> (raw)
In-Reply-To: <20040604233726.4FA074B104@berman.michael-chastain.com>
On Fri, Jun 04, 2004 at 07:37:26PM -0400, Michael Elizabeth Chastain wrote:
>Chris Faylor writes:
>cgf> If we have someone as a maintainer then it seems like their area of
>cgf> maintainership should reflect their vision, i.e. you can't just give
>cgf> carte blanche to a group people to do whatever they want in that arena.
>
>I think it might be good for me to state my vision. This is all
>stuff that y'all know about me already.
>
>(1) Copyright -- is the most important thing to me. I want every file
> in testsuite/ to bear a valid FSF copyright notice.
>
>(2) Testing submissions -- I mean to require that every patch says
> how it was tested (or not tested). I don't think it's useful
> to formalize or standardize how a patch is tested beyond that.
Does that translate into every bug reported eventually gets a test?
Would it make sense to add the test for a reported bug before a patch to
fix it is submitted?
I don't know who would be tasked with doing something like that but it
would sort of make sure that no bug was lost as the test suite FAILs
steadily rise...
cgf
next prev parent reply other threads:[~2004-06-04 23:57 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 [this message]
2004-06-05 0:17 ` Peter Barada
2004-06-05 10:09 ` Eli Zaretskii
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=20040604235736.GA3283@coe.casa.cgf.cx \
--to=me@cgf.cx \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).