From: David Carlton <carlton@kealia.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@redhat.com, drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa] create testsuite/gdb.cp directory
Date: Fri, 15 Aug 2003 15:48:00 -0000 [thread overview]
Message-ID: <yf21xvmylah.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <200308151534.h7FFYVfi015447@duracef.shout.net> (Michael Elizabeth Chastain's message of "Fri, 15 Aug 2003 11:34:31 -0400")
On Fri, 15 Aug 2003 11:34:31 -0400, Michael Elizabeth Chastain <mec@shout.net> said:
> Okay, I will revise my formal proposal to do what everybody wants:
> (1) create testsuite/gdb.cp
> (2) "cvs add" all the files from gdb.c++/* to gdb/cp
> (3) "cvs remove" all the files from gdb.c++
Great!
> (4) All this in gdb HEAD, no action in gdb gdb_6_0-branch
> I am open to changing (4) and doing it in the branch as well if
> David and Andrew want that (and I always care about Daniel's opinion
> as well).
I guess I have a slight preference for doing it on the branch as well.
The main difference seems to be that, if we don't, it will make future
mainline/6.0 comparisons harder but 6.0/5.3 comparisons easier,
whereas, if we do, it will make mainline/6.0 comparisons easier but
6.0/5.3 comparisons harder. Given that 6.0 is about to be released
(right?), 6.0/5.3 comparisons should soon become mostly irrelevant.
Also, it will make it easier to apply testsuite patches to both the
mainline and branch, when appropriate.
Having said that, I don't really care much at all one way or another.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-08-15 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 15:34 Michael Elizabeth Chastain
2003-08-15 15:48 ` David Carlton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-14 18:18 Michael Elizabeth Chastain
2003-08-15 15:52 ` Andrew Cagney
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=yf21xvmylah.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=ac131313@redhat.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