From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: psainty@orcon.net.nz, Ulrich.Windl@rz.uni-regensburg.de,
20403@debbugs.gnu.org
Subject: bug#20403: Format of NEWS (navigating in it)
Date: Fri, 01 Nov 2019 08:27:23 +0200 [thread overview]
Message-ID: <83sgn8m7qs.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=VbGgaXcOOK=7rUSx4o7nzzu496D6FALR+3_8FGEcxhA@mail.gmail.com> (message from Stefan Kangas on Fri, 1 Nov 2019 06:02:42 +0100)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 1 Nov 2019 06:02:42 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>, Phil Sainty <psainty@orcon.net.nz>,
> Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, 20403@debbugs.gnu.org
>
> Glenn Morris <rgm@gnu.org> writes:
>
> > Maybe the etc/NEWS symlink doesn't even need to be versioned.
> > The build process could construct it based on the version number.
>
> That makes sense to me. When creating source distribution tarballs,
> the file could simpy be copied or moved into place in case there are
> problems with symlinks on this or that platform (I guess MS-Windows?).
Tarballs with symlinks are problematic, so I'm against having symlinks
in the release tarball. But we could make NEWS a copy of the
corresponding NEWS.XY when we produce the tarball, if that's what
people prefer.
next prev parent reply other threads:[~2019-11-01 6:27 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
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 [this message]
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=83sgn8m7qs.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).