Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [RFA] Fix regression in "commands"
Date: Fri, 01 Dec 2017 16:56:00 -0000	[thread overview]
Message-ID: <87r2se5qv0.fsf@tromey.com> (raw)
In-Reply-To: <3a860acf-6e64-b2ba-e3fd-560406077259@redhat.com> (Pedro Alves's	message of "Tue, 7 Nov 2017 10:49:15 +0000")

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> I wonder whether gdb.base/commands.exp is a better home for this.

That file has some tests of "commands" but also is a grab-bag of testing
random commands.  I don't think the name specifically has to do with the
"commands" command; so unless you feel strongly about it, I'll just
leave it in break.exp.

Tom


  parent reply	other threads:[~2017-12-01 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 19:07 Tom Tromey
     [not found] ` <3a860acf-6e64-b2ba-e3fd-560406077259@redhat.com>
2017-12-01 16:45   ` Tom Tromey
2017-12-04 15:50     ` Pedro Alves
2017-12-07 18:13       ` Tom Tromey
2017-12-07 18:27         ` Pedro Alves
2017-12-01 16:56   ` Tom Tromey [this message]
2017-12-04 15:55     ` Pedro Alves

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=87r2se5qv0.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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