From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: carlton@kealia.com, drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa] create testsuite/gdb.cp directory
Date: Fri, 15 Aug 2003 15:52:00 -0000 [thread overview]
Message-ID: <3F3CF8DC.8090201@redhat.com> (raw)
In-Reply-To: <200308141818.h7EIIP4N032424@duracef.shout.net>
> 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
next prev parent reply other threads:[~2003-08-15 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 18:18 Michael Elizabeth Chastain
2003-08-15 15:52 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-15 15:34 Michael Elizabeth Chastain
2003-08-15 15:48 ` David Carlton
2003-08-14 18:10 Michael Elizabeth Chastain
2003-08-14 18:12 ` Daniel Jacobowitz
2003-08-14 18:12 ` 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=3F3CF8DC.8090201@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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