From: Tom Tromey <tom@tromey.com>
To: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Cc: gdb-patches@sourceware.org, gbenson@redhat.com
Subject: Re: [PATCH] Remove directory names from gdb.base/batch-exit-status.exp
Date: Thu, 01 Aug 2019 18:13:00 -0000 [thread overview]
Message-ID: <87k1bwah4l.fsf@tromey.com> (raw)
In-Reply-To: <20190730180848.16329-1-pedromfc@linux.ibm.com> (Pedro Franco de Carvalho's message of "Tue, 30 Jul 2019 15:08:48 -0300")
>>>>> "Pedro" == Pedro Franco de Carvalho <pedromfc@linux.ibm.com> writes:
Pedro> Adjust gdb.base/batch-exit-status.exp so that test prefixes don't show
Pedro> directory names for the source scripts passed with -x, to make test
Pedro> results from different build directories comparable.
Pedro> gdb/testsuite/ChangeLog:
Pedro> YYYY-MM-DD Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Pedro> * gdb.base/batch-exit-status.exp: Call test_exit_status with
Pedro> prefix argument.
Pedro> (test_exit_status): Add prefix argument.
Thanks, this is ok.
Tom
next prev parent reply other threads:[~2019-08-01 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 18:09 Pedro Franco de Carvalho
2019-08-01 18:13 ` Tom Tromey [this message]
2019-08-01 19:55 ` Pedro Franco de Carvalho
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=87k1bwah4l.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedromfc@linux.ibm.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