From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org, philippe.waroquiers@skynet.be
Subject: Re: [RFAv2 4/4] Document define-prefix command and the use of . in command names.
Date: Wed, 27 Nov 2019 05:21:00 -0000 [thread overview]
Message-ID: <83muchrj28.fsf@gnu.org> (raw)
In-Reply-To: <20191126233423.14801-5-philippe.waroquiers@skynet.be> (message from Philippe Waroquiers on Wed, 27 Nov 2019 00:34:23 +0100)
> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Date: Wed, 27 Nov 2019 00:34:23 +0100
>
> gdb/ChangeLog
> YYYY-MM-DD Philippe Waroquiers <philippe.waroquiers@skynet.be>
> * NEWS: Mention define-prefix. Tell that command names can now
> contain a . character.
>
> gdb/doc/ChangeLog
> YYYY-MM-DD Philippe Waroquiers <philippe.waroquiers@skynet.be>
>
> * gdb.texinfo (Define): Indicate that user-defined prefix can
> be used in 'define' command. Document 'define-prefix' command.
OK, thanks.
next prev parent reply other threads:[~2019-11-27 5:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 23:34 [RFAv2 0/4] More flexible user-defined commands prefixing and naming Philippe Waroquiers
2019-11-26 23:34 ` [RFAv2 3/4] Allow . character as part of command names Philippe Waroquiers
2019-11-27 21:44 ` Simon Marchi
2019-11-26 23:34 ` [RFAv2 4/4] Document define-prefix command and the use of . in " Philippe Waroquiers
2019-11-27 5:21 ` Eli Zaretskii [this message]
2019-11-26 23:34 ` [RFAv2 1/4] Implement user defined prefix Philippe Waroquiers
2019-11-27 21:37 ` Simon Marchi
2019-11-26 23:34 ` [RFAv2 2/4] Test define-prefix Philippe Waroquiers
2019-11-27 21:43 ` Simon Marchi
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=83muchrj28.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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).