From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Removal of markup annotations
Date: Tue, 21 Jun 2005 07:32:00 -0000 [thread overview]
Message-ID: <17079.49877.427388.19313@farnswood.snap.net.nz> (raw)
In-Reply-To: <ud5qgz5h5.fsf@gnu.org>
> > Its related to "History" which also isn't about controlling GDB, so perhaps
> > that node should also be moved
>
> Maybe we simply should describe the "server CMD" feature in the
> "History" node, instead of having it in a separate node.
That seems sensible. I can see now that "History" is in "Controlling GDB"
because it describes the setting of parameters. However, I think the
"Commands" section might be a better place. I think "History" should also be
called "Command History" to differentiate it from "Values History".
Nick
next prev parent reply other threads:[~2005-06-21 7:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 3:19 Nick Roberts
2005-06-15 15:41 ` Bob Rossi
2005-06-15 23:07 ` Nick Roberts
2005-06-15 23:35 ` Bob Rossi
2005-06-15 23:58 ` Nick Roberts
2005-06-21 1:41 ` Bob Rossi
2005-06-21 6:00 ` Nick Roberts
2005-06-21 10:22 ` Bob Rossi
2005-06-16 3:28 ` Eli Zaretskii
2005-06-15 17:06 ` Eli Zaretskii
2005-06-15 21:41 ` Nick Roberts
2005-06-20 11:54 ` Nick Roberts
2005-06-20 19:29 ` Eli Zaretskii
2005-06-20 21:48 ` Nick Roberts
2005-06-21 3:41 ` Eli Zaretskii
2005-06-21 7:32 ` Nick Roberts [this message]
[not found] ` <uacljzbgq.fsf@gnu.org>
2005-06-21 23:47 ` Nick Roberts
2005-06-22 3:25 ` Eli Zaretskii
2005-06-22 6:22 ` Nick Roberts
2005-07-03 19:04 ` Daniel Jacobowitz
2005-07-03 22:13 ` Nick Roberts
2005-07-03 22:45 ` Daniel Jacobowitz
2005-09-28 0:17 ` Nick Roberts
2005-09-28 2:39 ` Bob Rossi
2005-09-28 3:45 ` Daniel Jacobowitz
2005-09-28 6:40 ` Nick Roberts
2005-09-28 13:11 ` Daniel Jacobowitz
2005-09-28 22:52 ` Nick Roberts
2005-09-28 22:56 ` Daniel Jacobowitz
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=17079.49877.427388.19313@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=eliz@gnu.org \
--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