public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: Wolfgang Bangerth <bangerth@ices.utexas.edu>
Cc: Daniel Berlin <dberlin@dberlin.org>,
	Giovanni Bajo <giovannibajo@libero.it>,
	Volker Reichelt <reichelt@igpm.rwth-aachen.de>,
	gcc@gcc.gnu.org
Subject: Re: Suggestion for a new GNATS policy
Date: Mon, 12 May 2003 16:35:00 -0000	[thread overview]
Message-ID: <1052757240.729.53.camel@steven> (raw)
In-Reply-To: <Pine.LNX.4.44.0305120930050.15700-100000@gandalf.ices.utexas.edu>

Op ma 12-05-2003, om 16:39 schreef Wolfgang Bangerth:
> > I can make a radio button labeled "Reconfirm" (right under "Leave as 
> > NEW") for you  guys if you want, so it's just "select reconfirm, click 
> > commit".
> 
> That's cool. I also like the "minimized" and "verified" flags (which 
> indeed are really boolean flags).
> 
> Thanks for you work and responsiveness on all this, Daniel!

Wild idea:

What I'd really like to see is a "minimized test case" field (which may
be a pointer to an attachment) and an SQL query to extract them all.  

That way, people could put DejaGNU-ified test cases in the bug database,
rip them all out with the query, and test them on their target.  Even if
only a few people would to that, we would know much sooner if/when a bug
got fixed unnoticed (ie. PR not in CVS commit msg.), and to which target
the bug applies.

The idea is that we really would like to be able to batch-test PR
reports.  Janis and Wolfgang have talked about a PR testsuite, and this
idea was mentioned again earlier in this thread, but we really don't
want to litter the test suite that much.  With an easy way to extract
all minimized test cases, you'd effectively have the same thing without
even touching the testsuite.

Thoughts?

Greetz
Steven


  reply	other threads:[~2003-05-12 16:35 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11 22:24 Volker Reichelt
2003-05-12  1:56 ` Daniel Berlin
2003-05-12  2:03   ` Giovanni Bajo
2003-05-12  2:23     ` Daniel Berlin
2003-05-12  2:51       ` Giovanni Bajo
2003-05-12  4:16         ` Daniel Berlin
2003-05-12 10:59           ` Christian Ehrhardt
2003-05-12 13:46             ` Daniel Berlin
2003-05-12 14:28               ` Wolfgang Bangerth
2003-05-12 17:42                 ` Daniel Berlin
2003-05-12 18:19                   ` Wolfgang Bangerth
2003-05-12 16:36               ` Steven Bosscher
2003-05-12 16:38                 ` Wolfgang Bangerth
2003-05-12 13:53             ` Daniel Berlin
2003-05-12 15:10               ` Christian Ehrhardt
2003-05-12 15:57                 ` Wolfgang Bangerth
2003-05-12 14:39           ` Wolfgang Bangerth
2003-05-12 16:35             ` Steven Bosscher [this message]
2003-05-12 18:04               ` Janis Johnson
2003-05-12 18:57               ` Daniel Berlin
2003-05-12 17:58             ` Daniel Berlin
2003-05-12 18:24               ` Wolfgang Bangerth
2003-05-12 14:48       ` Wolfgang Bangerth
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 16:44 Nathanael Nerode
2003-05-12 16:37 Nathanael Nerode
2003-05-12 16:34 Nathanael Nerode
2003-05-11 21:52 S. Bosscher
2003-05-12  0:58 ` Daniel Berlin
2003-05-12  2:00   ` Giovanni Bajo
2003-05-12  3:10     ` Daniel Berlin
2003-05-12  1:24 ` Daniel Berlin
2003-05-12 14:50 ` Wolfgang Bangerth
2003-05-12 18:56   ` Daniel Berlin
2003-05-11 20:31 Volker Reichelt
2003-05-11 20:46 ` Daniel Berlin
2003-05-11 20:55 ` Joseph S. Myers
2003-05-12  0:51   ` Daniel Berlin
2003-05-12  2:08   ` Giovanni Bajo
2003-05-12  2:40     ` Gabriel Dos Reis
2003-05-12 17:29     ` Janis Johnson
2003-05-12 14:55   ` Wolfgang Bangerth

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=1052757240.729.53.camel@steven \
    --to=s.bosscher@student.tudelft.nl \
    --cc=bangerth@ices.utexas.edu \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=giovannibajo@libero.it \
    --cc=reichelt@igpm.rwth-aachen.de \
    /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).