public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Make test names unique in gdb.base/maint.exp
Date: Fri, 04 May 2018 15:33:00 -0000	[thread overview]
Message-ID: <bf863b8e-fcd5-978d-93c1-0fcd9093010e@redhat.com> (raw)
In-Reply-To: <20180504150252.21019-1-andrew.burgess@embecosm.com>

On 05/04/2018 04:02 PM, Andrew Burgess wrote:
> Add prefixes or suffixes to some test names to make them unique.
> 
> Replace a send_gdb/gdb_expect with a gdb_test, and make the test name
> unique.
> 
> Remove test of 'help maint' as this is already covered by a later call
> to test_prefix_command_help.
> 
> Removed test of 'help maint info' and add a new call to
> test_prefix_command_help instead.
> 
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.base/maint.exp: Make test names unique, use
> 	test_prefix_command_help to test 'help maint info', and remove
> 	repeated test of 'help maint'.

OK.

Thanks,
Pedro Alves

      reply	other threads:[~2018-05-04 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 15:03 Andrew Burgess
2018-05-04 15:33 ` Pedro Alves [this message]

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=bf863b8e-fcd5-978d-93c1-0fcd9093010e@redhat.com \
    --to=palves@redhat.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).