From: "J. Johnston" <jjohnstn@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patch for gdb/mi problem 702
Date: Wed, 23 Oct 2002 16:58:00 -0000 [thread overview]
Message-ID: <3DB7379E.A11BC7CF@redhat.com> (raw)
In-Reply-To: <3DB724FF.7040906@redhat.com>
Andrew Cagney wrote:
>
> > I have added test scenarios to gdb.mi testsuite to verify the new assign/update
> > behavior.
> >
> > gdb/testsuite/gdb.mi/ChangeLog
> >
> > 2002-10-23 Jeff Johnston <jjohnstn@redhat.com>
> >
> > * mi-var-cmd.exp: Add tests to verify that a -var-assign that changes
> > a value shows up in the changelist of a -var-update.
> > * mi1-var-cmd.exp: Ditto.
> >
> > Andrew, are you satisfied with my answer to your previous question
>
> Yep.
>
> > and may I commit
> > the original patch plus these changes?
>
> Yep, but. Can you just quickly check that, within each MI file, the new
> test messages are unique.
>
Confirmed.
> Please also add something to the NEWS file.
>
Done. Also added the other fixes I have added recently.
Patches committed.
-- Jeff J.
next prev parent reply other threads:[~2002-10-23 23:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 16:06 J. Johnston
2002-10-03 17:22 ` Keith Seitz
2002-10-04 9:57 ` J. Johnston
2002-10-04 10:12 ` Keith Seitz
2002-10-04 10:26 ` Alain Magloire
2002-10-04 12:26 ` J. Johnston
2002-10-04 14:35 ` Keith Seitz
2002-10-23 15:20 ` J. Johnston
2002-10-23 15:39 ` Andrew Cagney
2002-10-23 16:58 ` J. Johnston [this message]
2002-10-23 15:43 ` Andrew Cagney
2002-11-08 14:08 ` J. Johnston
2002-11-09 14:02 ` Eli Zaretskii
2002-11-11 9:12 ` J. Johnston
2002-10-21 18:40 ` Andrew Cagney
2002-10-22 14:54 ` J. Johnston
[not found] <200210041725.NAA27681@node1.ott.qnx.com>
2002-10-04 10:51 ` Keith Seitz
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=3DB7379E.A11BC7CF@redhat.com \
--to=jjohnstn@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.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