From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: master fb061cd 1/4: ; * etc/NEWS: Rearrange and fix wording of some entries.
Date: Wed, 08 Sep 2021 19:29:28 +0300 [thread overview]
Message-ID: <8335qfm3o7.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm7vUHhQdf+uUKiiAq7eVvQfbUxe0zktKZxhQDNQCmnoA@mail.gmail.com> (message from Stefan Kangas on Wed, 8 Sep 2021 18:06:38 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 8 Sep 2021 18:06:38 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> > users will be oblivious to that change, unless the install packages
> > from ELPA. The original entry, as stand-alone text, doesn't have any
> > practical impact on users that don't install packages, and would just
> > leave them wondering what is all this about.
> >
> > IOW, the changed default doesn't affect anyone who doesn't use
> > package.el. Which is why I moved it under that section.
>
> Could this concern be addressed by adding 2-3 lines that explains what
> it is about?
As I wrote elsewhere, announcing such changes in the Emacs ecosystem
is not the intended purpose of NEWS. So I'm against cluttering it
with stuff that does not directly contribute to its purpose: describe
changes in using Emacs to users who are familiar with past releases.
NEWS is too big already.
next prev parent reply other threads:[~2021-09-08 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210906101353.11322.30746@vcs0.savannah.gnu.org>
[not found] ` <20210906101355.082C520A0A@vcs0.savannah.gnu.org>
2021-09-06 18:33 ` master fb061cd 1/4: ; * etc/NEWS: Rearrange and fix wording of some entries Stefan Kangas
2021-09-06 18:46 ` Eli Zaretskii
2021-09-06 18:49 ` Eli Zaretskii
2021-09-08 16:06 ` Stefan Kangas
2021-09-08 16:29 ` Eli Zaretskii [this message]
2021-09-08 15:26 ` Amin Bandali
2021-09-08 15:58 ` Eli Zaretskii
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=8335qfm3o7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
/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).