From: Paul Hilfinger <hilfingr@tully.CS.Berkeley.EDU>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Have block_innermost_frame start from selected frame
Date: Mon, 09 Jan 2012 19:59:00 -0000 [thread overview]
Message-ID: <12815.1326139126@tully.CS.Berkeley.EDU> (raw)
In-Reply-To: Your message of Mon, 09 Jan 2012 19:13:28 +0200. <83sjjoer47.fsf@gnu.org>
> > Eli, your actual comment was a question about whether the syntax
> > applied to watch (given that all the examples used print). On
> > consideration, I decided to keep things as they are
>
> What does this mean? what exactly did you leave unchanged?
>
> And do I need to review the doc patch again, or is it largely
> unchanged?
>
Sorry. I meant that you should not have to review the doc/ part of the
patch, which is unchanged since the last time I submitted it. I did not
add any text specific to watchpoints, etc., on the grounds that the
entire chapter already appears intended to describe expressions in
general, and apparently has been understood as such up until now.
Thanks.
Paul
next prev parent reply other threads:[~2012-01-09 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 21:54 Paul Hilfinger
2011-12-31 8:58 ` Eli Zaretskii
2011-12-31 21:40 ` Paul Hilfinger
2012-01-09 7:17 ` Paul Hilfinger
2012-01-09 17:14 ` Eli Zaretskii
2012-01-09 19:59 ` Paul Hilfinger [this message]
2012-01-10 5:21 ` Joel Brobecker
2012-01-10 10:28 ` Eli Zaretskii
2012-01-10 10:40 ` Joel Brobecker
2012-01-11 10:59 ` [PATCH 1/3] Have block_innermost_frame start from selected frame and document Hilfinger
2012-01-11 15:54 ` [PATCH 2/3] Add testcase for locals identified with FUNCTION::VAR syntax Hilfinger
2012-01-11 10:59 ` [PATCH 3/3] Add test for use of "<block>::<variable>" syntax for locals in watch Hilfinger
-- strict thread matches above, loose matches on Subject: below --
2011-12-27 19:59 [RFA] Have block_innermost_frame start from selected frame Paul Hilfinger
2011-12-28 13:10 ` Jan Kratochvil
2011-12-28 15:41 ` Joel Brobecker
2011-12-28 16:00 ` Jan Kratochvil
2011-12-28 17:23 ` Joel Brobecker
2011-12-29 20:30 ` Paul Hilfinger
2011-12-29 23:13 ` Jan Kratochvil
2011-12-28 15:16 ` Jan Kratochvil
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=12815.1326139126@tully.CS.Berkeley.EDU \
--to=hilfingr@tully.cs.berkeley.edu \
--cc=Hilfinger@CS.Berkeley.EDU \
--cc=eliz@gnu.org \
--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).