From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: 24589@debbugs.gnu.org
Subject: bug#24589: [PATCH 0/2] Fix for command-debug-status
Date: Sun, 2 Oct 2016 18:59:53 +0200 [thread overview]
Message-ID: <20161002165955.2160-1-philippe.vaucher@gmail.com> (raw)
Hello,
This patch series restore the lost functionality of variable command-debug-status and also deprecate it in order for it to be removed in the future.
Regards,
Philippe Vaucher (2):
Restore command-debug-status functionality
Deprecate variable command-debug-status
doc/lispref/debugging.texi | 2 ++
lisp/subr.el | 2 ++
src/callint.c | 5 ++++-
3 files changed, 8 insertions(+), 1 deletion(-)
--
2.10.0
next reply other threads:[~2016-10-02 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 16:59 Philippe Vaucher [this message]
2016-10-02 16:59 ` bug#24588: [PATCH 1/2] Restore command-debug-status functionality Philippe Vaucher
2016-10-02 16:59 ` bug#24590: [PATCH 2/2] Deprecate variable command-debug-status Philippe Vaucher
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161002165955.2160-1-philippe.vaucher@gmail.com \
--to=philippe.vaucher@gmail.com \
--cc=24589@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).