From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: RFC - changes to the test suite
Date: Mon, 18 Feb 2013 19:20:00 -0000 [thread overview]
Message-ID: <20130218192027.GB22175@adacore.com> (raw)
In-Reply-To: <87fw0ta4jk.fsf@fleche.redhat.com>
> In the interest of nicer test isolation, I changed where the test suite
> places most files. For a given test file, say gdb.DIR/FILE.exp, the
> various output files (executables, .o files, libraries, etc) go in a new
> directory named "./outputs/gdb.DIR/FILE".
>
> This has two nice effects.
IMO, that would be a great improvement. This renders moot the exact
problem you are mentioning of trying to cleanup the gdb.ada directory.
In terms of the directory name itself, no preference.
--
Joel
next prev parent reply other threads:[~2013-02-18 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 17:57 Tom Tromey
2013-02-18 19:20 ` Joel Brobecker [this message]
2013-02-18 19:40 ` Jan Kratochvil
2013-02-18 20:46 ` Tom Tromey
2013-02-19 5:10 ` Jan Kratochvil
2013-02-19 6:40 ` Yao Qi
2013-02-26 19:00 ` 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=20130218192027.GB22175@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@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