From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27479 invoked by alias); 15 Aug 2003 15:52:20 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27472 invoked from network); 15 Aug 2003 15:52:19 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 15 Aug 2003 15:52:19 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 54E2E2B89; Fri, 15 Aug 2003 11:14:36 -0400 (EDT) Message-ID: <3F3CF8DC.8090201@redhat.com> Date: Fri, 15 Aug 2003 15:52:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Elizabeth Chastain Cc: carlton@kealia.com, drow@mvista.com, gdb-patches@sources.redhat.com Subject: Re: [rfa] create testsuite/gdb.cp directory References: <200308141818.h7EIIP4N032424@duracef.shout.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-08/txt/msg00246.txt.bz2 > dc> Why not move all the existing scripts to the new directory? That's > dc> what I'd prefer. > > I'm okay with that. But it would kill the cvs history of the tests, > and it would hurt people doing 'diff' on test runs from before and > after the change (such as gdb 6 to HEAD, after gdb 6 is released). > It wouldn't hurt my test bed because I use a 1000-line Perl script, > not diff, so I can adapt to test name changes. > > So I'll subdivide my proposal: > > (1) Create new directory gdb.cp > (2) Move all existing tests from gdb.c++ to gdb.cp > > I have no objection to (2). But if anyone objects to (2), > then I still want to do (1), with or without (2). There should be only one C++ testsuite directory: gdb.c++ XOR gdb.cp. Otherwize general confusion will result and, no matter how good everyones intent, new gdb.c++/* tests will eventually be added. I'd not put much weight on CVS stupidity. Limitations of the configure tool should not be used as an excuse for failing to fix a problem :-) enjoy, Andrew