From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Madhu <enometh@meer.net>, adam@alphapapa.net, emacs-devel@gnu.org
Subject: Re: please consider keeping defadvice around
Date: Mon, 11 Sep 2023 20:51:17 +0800 [thread overview]
Message-ID: <87msxs98l6.fsf@yahoo.com> (raw)
In-Reply-To: <83pm2orj2f.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Sep 2023 15:27:36 +0300")
Folks, defadvice is merely obsolete -- no proposal to remove it has
hitherto surfaced.
I favor retaining defadvice indefinitely, of course, but the time for
making that decision is still many years in the future. Let's postpone
it until then: threads like this one uniformly regress into protracted
series of largely frivolous diatribes, whose counter-productivity is an
established uncontested fact. We've witnessed two this month. Do we
really need another?
prev parent reply other threads:[~2023-09-11 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 15:05 please consider keeping defadvice around Madhu
2023-09-10 8:46 ` Adam Porter
2023-09-11 1:50 ` Madhu
2023-09-11 2:28 ` Eli Zaretskii
2023-09-11 2:39 ` Madhu
2023-09-11 2:55 ` Emanuel Berg
2023-09-11 12:27 ` Eli Zaretskii
2023-09-11 12:51 ` Po Lu [this message]
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=87msxs98l6.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=adam@alphapapa.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=enometh@meer.net \
/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).