From: Eli Zaretskii <eliz@gnu.org>
To: fam@euphon.net
Cc: gdb-patches@sourceware.org, schwab@linux-m68k.org,
andrew.burgess@embecosm.com, pedro@palves.net, fam@euphon.net,
simark@simark.ca
Subject: Re: [PATCH v5 3/3] disass: Add texinfo doc for the /x modifier
Date: Sat, 26 Sep 2020 09:02:21 +0300 [thread overview]
Message-ID: <837dshrs7m.fsf@gnu.org> (raw)
In-Reply-To: <20200925195108.978324-4-fam@euphon.net>
> From: fam@euphon.net
> Cc: Andreas Schwab <schwab@linux-m68k.org>,
> Andrew Burgess <andrew.burgess@embecosm.com>,
> Pedro Alves <pedro@palves.net>,
> fam@euphon.net,
> Simon Marchi <simark@simark.ca>,
> Eli Zaretskii <eliz@gnu.org>
> Date: Fri, 25 Sep 2020 20:51:08 +0100
>
> From: Fam Zheng <famzheng@amazon.com>
>
> gdb/doc/ChangeLog:
>
> 2020-09-25 Fam Zheng <famzheng@amazon.com>
>
> * gdb.texinfo: Document /x modifier of disass command.
For patches in *.texinfo and *texi Texinfo source files, our
convention is to name the nodes in which you make the changes (as if
the node were a function). You can see examples of this in the Git
log messages of our repository.
Thanks.
next prev parent reply other threads:[~2020-09-26 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 19:51 [PATCH v5 0/3] disass: Add " fam
2020-09-25 19:51 ` [PATCH v5 1/3] disass: Add /x modifier to print offsets in hex fam
2020-09-25 19:51 ` [PATCH v5 2/3] disass: Add test for /x mode fam
2020-09-25 19:51 ` [PATCH v5 3/3] disass: Add texinfo doc for the /x modifier fam
2020-09-26 6:02 ` Eli Zaretskii [this message]
2020-09-26 7:35 ` Fam Zheng
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=837dshrs7m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=fam@euphon.net \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=schwab@linux-m68k.org \
--cc=simark@simark.ca \
/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).