From: Stefan Kangas <stefankangas@gmail.com>
To: emacs-devel@gnu.org
Subject: Generate NEWS.XX.Y.html file for Emacs website
Date: Thu, 15 Sep 2022 01:39:44 -0700 [thread overview]
Message-ID: <CADwFkmnzw_KJ1WtLx-J1FyRzJkyzdS=_RML2OCrdXRqNkYd8rw@mail.gmail.com> (raw)
[I'm creating a new thread for generating HTML versions of etc/NEWS for
the website. This is continued from the discussion starting here:
https://lists.gnu.org/r/emacs-devel/2022-09/msg00759.html ]
Eli Zaretskii <eliz@gnu.org> writes:
> [P]lease describe what is needed (which commands and packages, and how
> to use them) to produce this HTML version.
The command is:
./src/emacs -l admin/admin.el -f make-news-html-file
mv etc/NEWS.XX.Y.html $EMACS_WEBROOT/news
cd $EMACS_WEBROOT
cvs commit -m "Update NEWS.XX.Y.html" news/NEWS.XX.Y.html
Please see `make-news-html-file' in admin/admin.el for more details.
It's still a work in progress, of course, but I'm happy to work on it.
> Also, how will this HTML version be maintained, after it is produced.
The easiest option is to just leave the old generated HTML files alone
and update them only if absolutely necessary.
But it'd be better if we could generate HTML versions of all etc/NEWS.*
files whenever we make a new release. I didn't yet look into this, so I
don't know how realistic this is, but I have a hunch that it's doable.
Maybe we will only be able to do it for releases newer than Emacs 21 (or
something) though.
We would then also need to add some code to delete all the Emacs 28.2
stuff from "NEWS.28.1.html". Maybe we would want to trim out the Emacs
28.1 headlines from "NEWS.28.2.html"? I'm not sure.
The second option has the added benefit that any fixes or additions we
make in old NEWS files would eventually propagate to the website.
next reply other threads:[~2022-09-15 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 8:39 Stefan Kangas [this message]
2022-09-15 13:07 ` Generate NEWS.XX.Y.html file for Emacs website 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
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='CADwFkmnzw_KJ1WtLx-J1FyRzJkyzdS=_RML2OCrdXRqNkYd8rw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--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.