From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: [RFA/testsuite/ada] re-implement make clean & distclean
Date: Sun, 31 Dec 2006 18:05:00 -0000 [thread overview]
Message-ID: <20061231180454.GA21036@nevyn.them.org> (raw)
In-Reply-To: <20061231152743.GC3428@adacore.com>
On Sun, Dec 31, 2006 at 07:27:43PM +0400, Joel Brobecker wrote:
> > I don't object too strongly, though, if others like this approach.
> > I wouldn't put them in that directory anyway, just in gdb/testsuite/.
>
> Fortunately, I only suggest this for gdb.ada, so very few people would
> be impacted. Perhaps the lack of consistency is a bad thing?
We have the same problem all over the testsuite, really - no one keeps
the makefiles up to date any more.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-12-31 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 10:08 Joel Brobecker
2006-12-31 13:12 ` Mark Kettenis
2006-12-31 14:31 ` Joel Brobecker
2006-12-31 14:54 ` Jim Blandy
2006-12-31 15:19 ` Daniel Jacobowitz
2006-12-31 15:27 ` Joel Brobecker
2006-12-31 18:05 ` Daniel Jacobowitz [this message]
2007-01-01 14:14 ` Joel Brobecker
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=20061231180454.GA21036@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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