From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add shortcuts for "nexti" and "stepi" commands in Single-Key mode
Date: Thu, 13 Jul 2017 19:09:00 -0000 [thread overview]
Message-ID: <5e7030db-1254-faca-62eb-ca5e3ada8a5a@gmail.com> (raw)
In-Reply-To: <83iniwgnv3.fsf@gnu.org>
On 13/07/17 22:04, Eli Zaretskii wrote:
>> Cc: gdb-patches@sourceware.org
>> From: Ruslan Kabatsayev <b7.10110111@gmail.com>
>> Date: Thu, 13 Jul 2017 21:19:10 +0300
>>
>>>> gdb/ChangeLog:
>>>>
>>>> * tui/tui.c: Add "nexti" and "stepi" to the tui_commands list
>>>> * doc/gdb.texinfo: Document the new shortcuts in Single-Key mode
>>>
>>> This is fine with me, but please state in the ChangeLog the
>>> functions/globals where you make the changes, and for gdb.texinfo
>>> please state the name of the node (in parentheses). I think the
>>> existing ChangeLog entries show how we do that.
>>
>> gdb/ChangeLog:
>> * tui/tui.c (tui_commands): Add "nexti" and "stepi" to the tui_commands list
>> * doc/gdb.texinfo (TUI Single Key Mode): Document the new shortcuts in
>> Single-Key mode
>
> Yes, that's it, except that the lines should be broken at column 75,
> and there should be a period at the end of each sentence.
gdb/ChangeLog:
* tui/tui.c (tui_commands): Add "nexti" and "stepi" to the Single-Key
mode command list.
* doc/gdb.texinfo (TUI Single Key Mode): Document the new shortcuts in
Single-Key mode.
>
> Thanks.
>
next prev parent reply other threads:[~2017-07-13 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 6:13 Ruslan Kabatsayev
2017-07-13 15:59 ` Eli Zaretskii
2017-07-13 18:19 ` Ruslan Kabatsayev
2017-07-13 19:04 ` Eli Zaretskii
2017-07-13 19:09 ` Ruslan Kabatsayev [this message]
2017-07-13 19:41 ` Eli Zaretskii
2017-07-26 19:19 ` [PING][PATCH] " Ruslan Kabatsayev
2017-07-26 20:53 ` Simon Marchi
2017-07-27 6:00 ` Ruslan Kabatsayev
2017-07-27 8:19 ` Simon Marchi
2017-07-27 9:12 ` Ruslan Kabatsayev
2017-07-27 9:27 ` Simon Marchi
2017-08-04 5:48 ` Ruslan Kabatsayev
2017-08-04 13:29 ` Simon Marchi
2017-08-04 19:11 ` Ruslan Kabatsayev
2017-08-04 21:04 ` John Baldwin
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=5e7030db-1254-faca-62eb-ca5e3ada8a5a@gmail.com \
--to=b7.10110111@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