From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: bauerman@br.ibm.com, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [rfa][testsuite] Consolidade Python test functions in lib/gdb.exp.
Date: Tue, 19 May 2009 19:22:00 -0000 [thread overview]
Message-ID: <83k54cq4oe.fsf@gnu.org> (raw)
In-Reply-To: <20090519145908.GA24773@caradoc.them.org>
> Date: Tue, 19 May 2009 10:59:08 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, tromey@redhat.com,
> gdb-patches@sourceware.org
>
> On Tue, May 19, 2009 at 11:50:38AM -0300, Thiago Jung Bauermann wrote:
> > What do you think? Is it just fine to have the testcase files named
> > differently from the source files? There's not a strict 1:1 mapping
> > between them, but it's close.
>
> Won't the testcase files have the same 8.3 issues?
Yes, they will. Which is why I suggest to rename them as well, and
then the problem of file-name differences between source and testcase
files will vanish.
TIA
next prev parent reply other threads:[~2009-05-19 19:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 15:21 Thiago Jung Bauermann
2009-04-20 17:13 ` Tom Tromey
2009-04-20 17:23 ` Daniel Jacobowitz
2009-05-18 4:38 ` Thiago Jung Bauermann
2009-05-18 18:11 ` Eli Zaretskii
2009-05-19 14:50 ` Thiago Jung Bauermann
2009-05-19 14:59 ` Daniel Jacobowitz
2009-05-19 19:22 ` Eli Zaretskii [this message]
2009-05-19 22:21 ` Thiago Jung Bauermann
2009-05-20 3:11 ` Eli Zaretskii
2009-05-20 3:26 ` Thiago Jung Bauermann
2009-05-20 3:39 ` Daniel Jacobowitz
2009-05-20 13:18 ` Thiago Jung Bauermann
2009-05-20 14:59 ` Daniel Jacobowitz
2009-05-20 15:10 ` Thiago Jung Bauermann
2009-05-20 17:22 ` Eli Zaretskii
2009-05-20 19:39 ` Thiago Jung Bauermann
2009-05-20 20:00 ` Eli Zaretskii
2009-05-20 20:49 ` Thiago Jung Bauermann
2009-05-20 23:11 ` Joel Brobecker
2009-05-31 22:26 ` Thiago Jung Bauermann
2009-05-31 22:37 ` Thiago Jung Bauermann
2009-06-04 18:03 ` Tom Tromey
2009-05-28 0:43 ` 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=83k54cq4oe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bauerman@br.ibm.com \
--cc=drow@false.org \
--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