From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: remove a bunch of testsuite/**/configure scripts
Date: Tue, 01 Mar 2011 04:53:00 -0000 [thread overview]
Message-ID: <20110301045303.GI30306@adacore.com> (raw)
In-Reply-To: <m3vd037t85.fsf@fleche.redhat.com>
> I'd like to go a few step farther and remove both testsuite/configure
> and all the Makefile.in's, but the latter at least were recently updated
> to make "make clean" work, so I'm a little reluctant to do this.
I'm in favor of at least removing the configure script. For
the Makefiles (would we keep the master one in gdb/testsuite/?,
I'd say yes, at least as a first step), it's a tougher one. I think
it depends on what the consequences in terms of funtionality would
be. I don't mind losing "make clean" capability in the testsuite
area, but that might be problems for those who build in-tree
(sacrilege! :-).
--
Joel
next prev parent reply other threads:[~2011-03-01 4:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 22:03 Tom Tromey
2011-02-28 22:11 ` Andreas Schwab
2011-03-01 17:15 ` Tom Tromey
2011-03-01 4:53 ` Joel Brobecker [this message]
2011-03-01 17:20 ` Tom Tromey
2011-03-03 16:57 ` Tom Tromey
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=20110301045303.GI30306@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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