From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Generate NEWS.XX.Y.html file for Emacs website
Date: Sat, 17 Sep 2022 16:08:07 -0400 [thread overview]
Message-ID: <CADwFkmnqw1KUuUc5samDY390z8-qDrtdhcFqzVt4jcPZMYGV1A@mail.gmail.com> (raw)
In-Reply-To: <83v8plzuoi.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> It still included NEWS for Emacs 28.1. I thought we wanted to delete
> those, leaving just the news of the single release?
The idea came up to just have a single page per major version, which
incidentally simplified generating the files. (I was particularly happy
about the latter.)
That's why I added the headlines for the versions, and also anchors so
we would link to:
https://www.gnu.org/software/emacs/news/NEWS.28.html#28.1
https://www.gnu.org/software/emacs/news/NEWS.28.html#28.2
> Also, is it possible not to number the items? The Emacs 28.2 NEWS are
> short, so it doesn't matter much, but for a major release the numbers
> get to ridiculous values, IMO. Moreover, people will start reporting
> issues referencing these numbers, and we will have to reverse-engineer
> them back to NEWS items.
I think we can remove the numbers. I only kept them because it felt
easier to navigate such a large file with them, but I'm happy either way.
(The change would just be one liner to the org header.)
> Get ready for bug reports...
Of course. No good deed goes unpunished. ;-)
next prev parent reply other threads:[~2022-09-17 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 8:39 Generate NEWS.XX.Y.html file for Emacs website Stefan Kangas
2022-09-15 13:07 ` Eli Zaretskii
2022-09-15 17:45 ` Stefan Kangas
2022-09-15 18:42 ` Eli Zaretskii
2022-09-15 19:32 ` Stefan Kangas
2022-09-15 18:29 ` Filipp Gunbin
2022-09-15 19:32 ` Stefan Kangas
2022-09-16 15:14 ` Stefan Kangas
2022-09-17 18:50 ` Stefan Kangas
2022-09-17 19:07 ` Eli Zaretskii
2022-09-17 20:08 ` Stefan Kangas [this message]
2022-09-18 5:22 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmnqw1KUuUc5samDY390z8-qDrtdhcFqzVt4jcPZMYGV1A@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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.