From: Mark Kettenis <kettenis@chello.nl>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Rewrite testsuite/configure.in
Date: Tue, 31 Dec 2002 00:23:00 -0000 [thread overview]
Message-ID: <86ptrjhwui.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Daniel Jacobowitz's message of "Sat, 28 Dec 2002 19:07:51 -0500"
Daniel Jacobowitz <drow@mvista.com> writes:
> > If there are no objections, I'll check this in in a week or so.
>
> No objections, but: do you think it's possible to eliminate the need to
> configure in each individual subdir? It's moderately annoying, and I
> don't think we need it. About the only thing we use it for now is for
> "make clean" to clean up the testsuite directory.
I'm sure the majority of those configure scripts can be avoided.
Creating the Makefiles in the subdirectories from the configure script
in the testsuite directory is no problem. So unless someone objects,
I'll start getting rid of the unneeded configure scripts once my
initial cleanup of testsuite/configure.in is checked in.
Mark
next prev parent reply other threads:[~2002-12-31 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 14:25 Mark Kettenis
2002-12-28 18:24 ` Daniel Jacobowitz
2002-12-29 11:04 ` Alexandre Oliva
2002-12-31 0:23 ` Mark Kettenis [this message]
2002-12-31 1:58 ` Jason Molenda
2003-01-04 0:44 Mark Kettenis
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=86ptrjhwui.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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