public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: bangerth@ticam.utexas.edu
Cc: ebotcazou@libertysurf.fr, jakub@redhat.com, gcc@gcc.gnu.org,
	janis187@us.ibm.com, ehrhardt@mathematik.uni-ulm.de
Subject: Re: A testcase library
Date: Fri, 20 Dec 2002 10:51:00 -0000	[thread overview]
Message-ID: <200212201713.SAA65489@numa6.igpm.rwth-aachen.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0212201010010.15464-100000@gandalf.ticam.utexas.edu>

On 20 Dec, Wolfgang Bangerth wrote:
> On Fri, 20 Dec 2002, Eric Botcazou wrote:
> 
>> > But that doesn't keep us from doing something similar in a different
>> > location. I had some discussion over the topic in private mail with
>> > Wolfgang and we decided to wait for Bugzilla before setting up something
>> > new. But maybe there are better suggestions?
>> 
>> Why not a special directory in the testsuite that is not tested by the 
>> toplevel 'make check' but by a magic-like command invoked only by 
>> those-who-know ? It would not be included in the official tarballs.
> 
> That was my original thought. It would allow us to get the presently 
> smallest testcase to check for something, and if we can further reduce it, 
> we could check in the new testcase as well. It would also allow potentail 
> bug fixers simpler access to the testcases.
> 
> On the other hand, the list of people with CVS write privileges would have 
> to be expanded.

We'd probably also want a looser check-in policy for the problem
reports.

Regards,
Volker


  reply	other threads:[~2002-12-20 16:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20  8:12 Volker Reichelt
2002-12-20  8:14 ` Jakub Jelinek
2002-12-20  8:50   ` Volker Reichelt
2002-12-20  9:12     ` Eric Botcazou
2002-12-20  9:32       ` Wolfgang Bangerth
2002-12-20 10:51         ` Volker Reichelt [this message]
2002-12-20 12:02     ` Jason R Thorpe
2002-12-22 22:44     ` Ben Elliston
2002-12-23 12:46       ` Mike Stump
2002-12-23 12:57         ` Daniel Jacobowitz
2002-12-23 15:54           ` Mike Stump
2002-12-23 16:35             ` Daniel Jacobowitz
2002-12-23 13:50         ` Ben Elliston
2002-12-23 14:00           ` Zack Weinberg
2002-12-23 15:27             ` Daniel Jacobowitz
2002-12-20 15:01   ` Joseph S. Myers
2002-12-23 18:08 Richard Kenner
2002-12-24 12:30 ` David Carlton
2002-12-23 18:42 Richard Kenner
2002-12-23 21:57 ` Daniel Jacobowitz
2002-12-24 12:28 ` David Carlton

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=200212201713.SAA65489@numa6.igpm.rwth-aachen.de \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=bangerth@ticam.utexas.edu \
    --cc=ebotcazou@libertysurf.fr \
    --cc=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=janis187@us.ibm.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).