From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: klee@apple.com
Cc: msnyder@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] add 'save-breakpoints' command
Date: Tue, 11 Dec 2001 09:09:00 -0000 [thread overview]
Message-ID: <7458-Tue11Dec2001190820+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <E16DprF-0001Hn-00@localhost> (message from Klee Dienes on Tue, 11 Dec 2001 11:34:17 -0500)
> From: Klee Dienes <klee@apple.com>
> Date: Tue, 11 Dec 2001 11:34:17 -0500
>
> . I'm certainly willing to document the additional convenience
> variables, but I'm not sure where a good section for them would be.
It sounds like I've misread the code: I thought restoring the
breakpoints also sets input-radix for the rest of the session. But I
understand now that the saved commands undo that effect before the
session continues, is that right? If so, there's no need to document
anything about that, except, perhaps, saying that the breakpoints,
when restored, will use the same input-radix as when they were
defined.
With that comment, the patch you posted is approved. Thanks.
next prev parent reply other threads:[~2001-12-11 17:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 10:21 Klee Dienes
2001-12-04 10:26 ` Daniel Jacobowitz
2001-12-04 10:44 ` Klee Dienes
2001-12-05 14:06 ` Tom Tromey
2001-12-04 11:22 ` Eli Zaretskii
2001-12-04 13:35 ` Klee Dienes
2001-12-05 0:25 ` Eli Zaretskii
2001-12-04 14:48 ` Michael Snyder
2001-12-04 21:11 ` Klee Dienes
2001-12-11 0:28 ` Klee Dienes
2001-12-11 3:55 ` Eli Zaretskii
2001-12-11 8:35 ` Klee Dienes
2001-12-11 9:09 ` Eli Zaretskii [this message]
2001-12-11 13:23 ` Klee Dienes
2001-12-12 0:32 ` Eli Zaretskii
2001-12-14 12:45 ` Klee Dienes
2001-12-14 12:50 ` Daniel Jacobowitz
2001-12-18 1:42 ` Klee Dienes
[not found] <1007594419.30359.ezmlm@sources.redhat.com>
2001-12-05 17:39 ` Jim Ingham
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=7458-Tue11Dec2001190820+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=klee@apple.com \
--cc=msnyder@cygnus.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