From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Ulrich.Windl@rz.uni-regensburg.de, stefan@marxist.se,
20403@debbugs.gnu.org
Subject: bug#20403: Format of NEWS (navigating in it)
Date: Thu, 31 Oct 2019 16:43:50 +0200 [thread overview]
Message-ID: <83eeytnffd.fsf@gnu.org> (raw)
In-Reply-To: <2ecef70596fda1bcaaaa31944a01a39a@webmail.orcon.net.nz> (message from Phil Sainty on Thu, 31 Oct 2019 22:56:50 +1300)
> Date: Thu, 31 Oct 2019 22:56:50 +1300
> From: Phil Sainty <psainty@orcon.net.nz>
> Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, 20403@debbugs.gnu.org
>
> The change I'd actually like to see is for NEWS to just be a symlink
> to the appropriate NEWS.xx file, which should exist under that name
> from the outset of development on version xx.
That'd cause trouble when merging from the release branch. Symlinks
complicate VCS operations in general.
If we want a better NEWS, I'd suggest to introduce a new mode, which
will inherit from Outline mode, but will support some sort of
"include" directive. Then we could have a NEWS file that just
"include"d the versioned files, and Emacs would display their
contents, perhaps given some user command to expand a given version's
news. As a bonus, this would let us have a single NEWS file, from
user's POV, like other (smaller) projects do.
next prev parent reply other threads:[~2019-10-31 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 6:14 bug#20403: Format of NEWS (navigating in it) Ulrich Windl
2019-09-30 0:24 ` Stefan Kangas
2019-10-30 20:34 ` Stefan Kangas
2019-10-31 9:56 ` Phil Sainty
2019-10-31 14:43 ` Eli Zaretskii [this message]
2019-10-31 16:04 ` Stefan Kangas
2019-10-31 16:11 ` Eli Zaretskii
2019-10-31 19:19 ` Glenn Morris
2019-10-31 20:08 ` Eli Zaretskii
2019-11-01 5:02 ` Stefan Kangas
2019-11-01 6:27 ` Eli Zaretskii
2019-11-11 19:06 ` Stefan Kangas
2019-11-04 7:16 ` bug#20403: Antw: " Ulrich Windl
2019-11-04 16:11 ` 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=83eeytnffd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20403@debbugs.gnu.org \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=psainty@orcon.net.nz \
--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).