From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Organizing the NEWS file a bit better
Date: Sat, 04 Sep 2021 21:04:39 +0200 [thread overview]
Message-ID: <87wnnwp3g8.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkm=eY4iySA=g8dbJuejaRvqsTvVPKXOn7sKXdpdxOCmpBg@mail.gmail.com> (Stefan Kangas's message of "Sat, 4 Sep 2021 20:53:22 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> I'm looking at re-organizing NEWS a bit, and I'm not sure how we prefer it.
>
> In general, I guess I also wonder if anyone will protest if I take it
> upon myself to move things around to more sensible places.
Please go ahead. When adding NEWS-worthy things, they generally land
somewhere in the general section where they should be, not organised
further than that. (I try to see if there's something already in NEWS
that's about the same package, and then create a sub-section for
that... but not methodically.)
> Here are some concrete questions:
>
> - Under "Changes in Specialized Modes and Packages" things seem thrown
> in more or less at random. Do we prefer to order it according to
> perceived order of importance? Would it make sense to organize it
> alphabetically?
I have no opinion about that.
> - Does "Tab Bars" belong under "Changes in Emacs" rather than
> "Specialized Modes"? It's more like a core feature to my mind, even
> if not everyone uses it. (I've moved "Windows" and "Frames" there
> already.)
Yes, sounds like a "Changes in Emacs" thing, I think.
> - Under "Incompatible Editing Changes" we have several items relating
> to specialized modes (f90-mode, nroff-mode, vc, project). Do these
> entries belong under "Specialized Modes and Packages"?
Uhm... I think it makes sense to have the incompatible stuff in one
section? It makes it easy for people who only want to know what might
have broken in their code.
> - Could we just put new headers for macOS and MS-Windows under "Emacs
> 28.1 on Non-Free Operating Systems"? Entries now start with "On
> macOS ..." or "On MS-Windows ...", which we could avoid.
Sounds good.
> - Under "Editing Changes" we have many things that doesn't seem like
> they belong there. Should they be moved? See the list below where
> I've marked things that we might want to move with "x".
Hm... where would you move them to? "Changes in Emacs"? I think most
of the "x" things might live more comfortably there, perhaps?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-04 19:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 18:53 Organizing the NEWS file a bit better Stefan Kangas
2021-09-04 19:04 ` Lars Ingebrigtsen [this message]
2021-09-04 19:34 ` Stefan Kangas
2021-09-04 19:47 ` Eli Zaretskii
2021-09-04 20:36 ` Tim Cross
2021-09-04 21:08 ` Stefan Kangas
2021-09-06 2:30 ` Stefan Kangas
2021-09-06 3:45 ` Jean-Christophe Helary
2021-09-06 6:35 ` Juri Linkov
2021-09-06 6:57 ` Stefan Kangas
2021-09-06 8:37 ` Lars Ingebrigtsen
2021-09-06 9:01 ` Stefan Kangas
2021-09-06 9:04 ` Lars Ingebrigtsen
2021-09-06 18:17 ` Stefan Kangas
2021-09-06 18:42 ` Eli Zaretskii
2021-09-06 18:57 ` Stefan Kangas
2021-09-06 19:18 ` Eli Zaretskii
2021-09-06 20:38 ` Stefan Kangas
2021-09-06 20:42 ` Stefan Kangas
2021-09-07 5:38 ` Eli Zaretskii
2021-09-07 6:47 ` Stefan Kangas
2021-09-07 6:53 ` Stefan Kangas
2021-09-07 8:12 ` Eli Zaretskii
2021-09-07 15:09 ` Lars Ingebrigtsen
2021-09-06 11:01 ` Eli Zaretskii
2021-09-06 11:07 ` Lars Ingebrigtsen
2021-09-06 11:20 ` Eli Zaretskii
2021-09-06 10:39 ` Eli Zaretskii
2021-09-06 10:14 ` Eli Zaretskii
2021-09-04 19:05 ` Juri Linkov
2021-09-04 19:16 ` Eli Zaretskii
2021-09-04 19:35 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnnwp3g8.fsf@gnus.org \
--to=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.