public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: reorder and group sections relating to aliases
Date: Fri, 22 Jan 2021 09:38:40 +0000	[thread overview]
Message-ID: <20210122093840.GA265215@embecosm.com> (raw)
In-Reply-To: <8335yu6pkn.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2021-01-21 21:46:16 +0200]:

> > Date: Thu, 21 Jan 2021 18:18:36 +0000
> > From: Andrew Burgess <andrew.burgess@embecosm.com>
> > Cc: Eli Zaretskii <eliz@gnu.org>
> > 
> > Thanks for the feedback.
> > 
> > The patch I pushed is below, I believe this addresses all of your
> > feedback.
> 
> Yes.  One nit is that @menu is better placed at the end of a node, not
> at its beginning.

Sorry about that.  I pushed the patch below to fix this.

Thanks,
Andrew

---

commit fe461d2f70ed618c39b887579d07f49f603c1de5
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date:   Fri Jan 22 09:28:07 2021 +0000

    gdb/doc: move @menu to the end of the node
    
    Commit:
    
      commit a72d0f3d69896b5fcdc916e0547fe774dcb58614
      Date:   Tue Jan 12 13:02:30 2021 +0000
    
          gdb/doc: reorder and group sections relating to aliases
    
    Added a @menu block into the wrong place within a @node.  This commit
    moves it to the end of the @node, where it should be been placed.
    
    gdb/doc/ChangeLog:
    
            * gdb.texinfo (Aliases): Move @menu to the end of the node.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index b4133413061..1335c9093c8 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -27455,10 +27455,6 @@
 @section Command Aliases
 @cindex aliases for commands
 
-@menu
-* Command aliases default args::	Default arguments for aliases
-@end menu
-
 Aliases allow you to define alternate spellings for existing commands.
 For example, if a new @value{GDBN} command defined in Python
 (@pxref{Python}) has a long name, it is handy to have an abbreviated
@@ -27557,6 +27553,10 @@
 (gdb) spe 20
 @end smallexample
 
+@menu
+* Command aliases default args::	Default arguments for aliases
+@end menu
+
 @node Command aliases default args
 @subsection Default Arguments
 @cindex aliases for commands, default arguments

      reply	other threads:[~2021-01-22  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 13:18 Andrew Burgess
2021-01-12 16:02 ` Eli Zaretskii
2021-01-12 17:01   ` Andrew Burgess
2021-01-13 15:04     ` Eli Zaretskii
2021-01-21 18:18       ` Andrew Burgess
2021-01-21 19:46         ` Eli Zaretskii
2021-01-22  9:38           ` Andrew Burgess [this message]

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=20210122093840.GA265215@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --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).