From: Stafford Horne <shorne@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] reggroups: Add test and docs for `info reg $reggroup` feature
Date: Thu, 08 Jun 2017 04:59:00 -0000 [thread overview]
Message-ID: <20170608045903.GA5971@lianli.shorne-pla.net> (raw)
In-Reply-To: <83efuv8aqk.fsf@gnu.org>
On Thu, Jun 08, 2017 at 05:38:27AM +0300, Eli Zaretskii wrote:
> > From: Stafford Horne <shorne@gmail.com>
> > Cc: Stafford Horne <shorne@gmail.com>
> > Date: Thu, 8 Jun 2017 07:15:45 +0900
> >
> > Until now this feature has existed but was not documented. Adding docs
> > and tests.
> >
> > gdb/ChangeLog:
> >
> > 2017-06-06 Stafford Horne <shorne@gmail.com>
> >
> > * doc/gdb.texinfo: Document info reg $reggroup feature.
>
> OK for the documentation part, but please state in the ChangeLog entry
> the name of the node(s) in which you make the change(s).
Thanks for the review, I didnt know about this for doc changes. I will
update.
next prev parent reply other threads:[~2017-06-08 4:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 22:15 [PATCH 0/3] Support for arbitrary reggroups Stafford Horne
2017-06-07 22:16 ` [PATCH 1/3] reggroups: Add test and docs for `info reg $reggroup` feature Stafford Horne
2017-06-08 2:38 ` Eli Zaretskii
2017-06-08 4:59 ` Stafford Horne [this message]
2017-06-08 20:31 ` Simon Marchi
2017-06-08 23:27 ` Stafford Horne
2017-06-09 6:20 ` Simon Marchi
2017-06-13 11:17 ` Pedro Alves
2017-06-07 22:16 ` [PATCH 3/3] tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p Stafford Horne
2017-06-08 2:40 ` Eli Zaretskii
2017-06-08 5:01 ` Stafford Horne
2017-06-08 14:56 ` Eli Zaretskii
2017-06-08 20:52 ` Simon Marchi
2017-06-09 11:45 ` Stafford Horne
2017-06-09 19:59 ` Simon Marchi
2017-06-10 8:17 ` Stafford Horne
2017-06-13 11:17 ` Pedro Alves
2017-06-07 22:16 ` [PATCH 2/3] reggroups: Convert reggroups from post_init to pre_init Stafford Horne
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=20170608045903.GA5971@lianli.shorne-pla.net \
--to=shorne@gmail.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).