From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, andrew.burgess@embecosm.com
Subject: Re: [PATCH 4/9] gdb/doc: Restructure frame command documentation.
Date: Fri, 11 Sep 2015 20:17:00 -0000 [thread overview]
Message-ID: <83si6k3e47.fsf@gnu.org> (raw)
In-Reply-To: <3f336520c7dfa1cd62646a2e8c6ab37cfc99aa7c.1441996064.git.andrew.burgess@embecosm.com>
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Fri, 11 Sep 2015 19:49:38 +0100
>
> The 'frame' command is documented in two places. The 'select-frame'
> command is only mentioned in one of these places.
>
> Of the two places, having the description of 'frame' and 'select-frame'
> in the section 'Selecting a Frame' seems like the most obvious choice,
> which is where things like 'up' and 'down' are also documented.
>
> This commit moves the documentation of 'frame' and 'select-frame' into
> the 'Selecting a Frame' section, and removes the duplicate documentation
> of the 'frame' command.
>
> At the same time I have reordered the sections in the 'Examining the
> Stack' chapter, moving the discussion of frame filters to the end of the
> chapter; it feels odd that we talk about frame filters before such basic
> things like navigating the stack, or examining stack frames in general.
OK, thanks.
next prev parent reply other threads:[~2015-09-11 20:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 18:49 [PATCH 0/9] Changes to frame selection Andrew Burgess
2015-09-11 18:49 ` [PATCH 2/9] gdb: Select a frame for frame_info Andrew Burgess
2015-09-11 18:50 ` [PATCH 5/9] gdb: Fix bug with dbx style func command Andrew Burgess
2015-09-30 13:47 ` Pedro Alves
2015-10-26 13:40 ` Thomas Preud'homme
2015-10-26 16:33 ` Andrew Burgess
2015-09-11 18:50 ` [PATCH 1/9] gdb: Check the selected-frame in frame_find_by_id Andrew Burgess
2015-09-30 13:40 ` Pedro Alves
2015-09-11 18:50 ` [PATCH 3/9] gdb: Make use of safe-ctype.h header Andrew Burgess
2015-09-30 13:43 ` Pedro Alves
2015-09-11 18:50 ` [PATCH 8/9] gdb: Split func_command into two parts Andrew Burgess
2015-09-30 13:52 ` Pedro Alves
2015-09-11 18:50 ` [PATCH 4/9] gdb/doc: Restructure frame command documentation Andrew Burgess
2015-09-11 20:17 ` Eli Zaretskii [this message]
2015-09-11 18:50 ` [PATCH 9/9] gdb: Change how frames are selected for 'frame' and 'info frame' Andrew Burgess
2015-09-11 20:21 ` Eli Zaretskii
2015-09-15 10:41 ` Andrew Burgess
2015-09-15 10:50 ` Eli Zaretskii
2015-09-17 11:36 ` Andrew Burgess
2015-09-30 14:00 ` Pedro Alves
2015-09-11 18:50 ` [PATCH 6/9] gdb: Avoid unneeded calls to parse_frame_specification Andrew Burgess
2015-09-30 13:48 ` Pedro Alves
2015-09-11 18:50 ` [PATCH 7/9] gdb: Simplify parse_frame_specification Andrew Burgess
2015-09-30 13:50 ` Pedro Alves
2015-10-12 21:43 ` [PATCH 0/9] Changes to frame selection Andrew Burgess
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=83si6k3e47.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--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