From: Eli Zaretskii <eliz@elta.co.il>
To: Michael Snyder <msnyder@redhat.com>
Cc: jim.houston@comcast.net, gdb-patches@sources.redhat.com
Subject: Re: [patch] allow switching stacks
Date: Tue, 09 Mar 2004 06:06:00 -0000 [thread overview]
Message-ID: <uishesgdi.fsf@elta.co.il> (raw)
Message-ID: <20040309060600.I_ehPjBxdgVWNKaZKO4bWZqXrTthNbDR60xN-x8ub7E@z> (raw)
In-Reply-To: <404CFA95.30204@redhat.com> (message from Michael Snyder on Mon, 08 Mar 2004 22:58:29 +0000)
> Date: Mon, 08 Mar 2004 22:58:29 +0000
> From: Michael Snyder <msnyder@redhat.com>
>
> Good idea, and nice implementation. My only suggestions are in
> the user interface realm. I'm thinking something like
> "non-contiguous stacks" would be more meaningful than "multiple
> stacks" (there's really still only one stack, it's just broken
> into two segments). Same goes for switch-stacks; it's a bit
> non-intuitive to me. segmented-stack? discontiguous-stack?
I share Muchael's concerns (I'd use "non-contiguous stack" in both
instances). On top of that, if this patch is approved, it needs a
corresponding patch for the manual, since we'd be introducing a new
command.
next prev parent reply other threads:[~2004-03-09 6:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 18:06 Jim Houston
2004-03-08 22:58 ` Michael Snyder
2004-03-19 0:09 ` Eli Zaretskii [this message]
2004-03-09 6:06 ` Eli Zaretskii
2004-03-19 0:09 ` Michael Snyder
2004-03-09 20:21 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-04-02 22:06 ` Andrew Cagney
2004-04-09 22:40 ` Daniel Jacobowitz
2004-04-12 21:05 ` Jim Blandy
2004-04-12 21:13 ` Daniel Jacobowitz
2004-03-19 0:09 ` Jim Houston
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=uishesgdi.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jim.houston@comcast.net \
--cc=msnyder@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