From: Iain Sandoe <iain@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFA, Patch, testsuite] gdb.base/list.exp: initial state test for stub targets.
Date: Fri, 15 Jun 2012 14:43:00 -0000 [thread overview]
Message-ID: <996B8C01-2D3A-4104-90EA-F63F3E690235@codesourcery.com> (raw)
In-Reply-To: <4FD88886.9030803@redhat.com>
On 13 Jun 2012, at 13:33, Pedro Alves wrote:
>
> Okay for (a) from me. But the ChangeLog entry should say what you did, not
> why you did it. Something like:
>
> * gdb.base/list.exp (test_listsize): Remove $use_gdb_stub special case.
> (top level): Use gdb_file_cmd instead of gdb_load.
thanks, applied with your recommended log,
Iain
prev parent reply other threads:[~2012-06-15 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 12:23 Iain Sandoe
2012-06-13 12:33 ` Pedro Alves
2012-06-15 14:43 ` Iain Sandoe [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=996B8C01-2D3A-4104-90EA-F63F3E690235@codesourcery.com \
--to=iain@codesourcery.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