Re: emacs-29 9b775ddc057 1/2: ; * etc/EGLOT-NEWS: Fix wording of last change.

[Eli Zaretskii <eliz@gnu.org>]

> Date: Mon, 08 May 2023 14:19:33 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: dmitry@gutov.dev, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> 
> > From: Philip Kaludercic <philipk@posteo.net>
> > Cc: dmitry@gutov.dev,  monnier@iro.umontreal.ca,  emacs-devel@gnu.org
> > Date: Sun, 07 May 2023 19:44:01 +0000
> > 
> > Eli Zaretskii <eliz@gnu.org> writes:
> > 
> > >> Packages to install: 23 (xref-1.6.3
> > >> verilog-mode-2022.12.18.181110314 use-package-2.4.5 tramp-2.6.0.4
> > >> svg-1.1 soap-client-3.2.1 so-long-1.1.2 python-0.28 project-0.9.8
> > >> org-9.6.5 ntlm-2.1.0 nadvice-0.4 map-3.3.1 let-alist-1.0.6
> > >> jsonrpc-1.0.17 flymake-1.3.4 external-completion-0.1 erc-5.5
> > >> eldoc-1.14.0 eglot-1.15 cl-lib-0.7.1 cl-generic-0.3 bind-key-2.4.1).
> > >> Packages to upgrade: 2 (editorconfig-0.9.1 inspector-0.29).
> > >> Proceed? (y or n)
> > >
> > > I see nothing unexpected in this list.  And since the feature is
> > > opt-in, what are the dangers of having it?
> > 
> > There is no danger, it might just be overwhelming?  I was a bit
> > surprised at first.  But if you think it is fine, then I have no
> > objections.
> 
> Assuming users who turn this on understand the meaning, I see no
> problem.  Once this is on the branch, I will take care of documenting
> this to make the consequences clear.

Done; comments welcome.