From: Eli Zaretskii <eliz@gnu.org>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: Directory Servers in Tools menu
Date: Mon, 16 Apr 2018 21:17:39 +0300 [thread overview]
Message-ID: <83po2z2eyk.fsf@gnu.org> (raw)
In-Reply-To: <m3vacs3ux3.fsf@fitzsim.org> (message from Thomas Fitzsimmons on Sun, 15 Apr 2018 19:35:20 -0400)
> From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Sun, 15 Apr 2018 19:35:20 -0400
>
> I looked at this. There are definitely some simplifications that I'd
> like to implement eventually, like deprecating then eliminating the
> eudc-options file, and allowing a single search to span multiple
> directory servers. However, an easy first step is deprecating then
> removing XEmacs support. Can I push this NEWS entry to the emacs-26
> branch?
>
> Thomas
>
> diff --git a/etc/NEWS b/etc/NEWS
> index 4b1f673a7c..f014bff99c 100644
> --- a/etc/NEWS
> +++ b/etc/NEWS
> @@ -733,6 +733,10 @@ with blank space to eshell history.
> major release of Emacs. Users of BBDB 2.x should plan to upgrade to
> BBDB 3.x.
>
> +*** Support for XEmacs is deprecated and will be removed in the next
> +major release of Emacs. XEmacs users can continue using this or a
> +prior version of EUDC.
Thanks, but I don't understand what is the practical meaning of such
an entry: it doesn't really reflect any real change in Emacs. The
deprecation doesn't have any expression in the code; using the code
you want to deprecate will not generate any warnings to the effect
that these features are deprecated.
What I suggest instead is to actually remove those parts from the
master branch and mention the removal in NEWS on that branch.
prev parent reply other threads:[~2018-04-16 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 2:45 Directory Servers in Tools menu Glenn Morris
2018-03-03 8:27 ` Eli Zaretskii
2018-03-03 19:31 ` Glenn Morris
2018-03-03 20:00 ` Eli Zaretskii
2018-03-05 18:44 ` Glenn Morris
2018-03-06 0:04 ` Thomas Fitzsimmons
2018-03-07 17:53 ` Glenn Morris
2018-04-15 23:35 ` Thomas Fitzsimmons
2018-04-16 18:17 ` Eli Zaretskii [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=83po2z2eyk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fitzsim@fitzsim.org \
--cc=rgm@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).