From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Karl Fogel <kfogel@red-bean.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 28.2 released
Date: Thu, 15 Sep 2022 00:44:15 -0700 [thread overview]
Message-ID: <CADwFkm=dEMWfNcLjP5ASHvoQg3RFsdsOkxsko7YQFQSws9e8+g@mail.gmail.com> (raw)
In-Reply-To: <83y1ulyvgx.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> AFAIU, you wanted to have there an HTML link to the NEWS file, is that
> correct? If so, I can suggest adding to the above text the link to
>
> https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-28
>
> Would that be okay?
That proposal sounds okay to me, FWIW.
> One subtle issue here is that when we post the email announcement
> about a new release, the on-line manuals and the Emacs Web page are
> not yet up-to-date, so either a link to anything inside the Web pages
> will be outdated, or we will need to delay the announcement until the
> Web pages are updated, both of which are undesirable. A link to Git
> above is thus a compromise that doesn't have these disadvantages.
That's exactly right. While I do happen to think there is room for more
automation here, the link to git is a good compromise for now.
next prev parent reply other threads:[~2022-09-15 7:44 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 17:06 Emacs 28.2 released Karl Fogel
2022-09-14 17:21 ` Eli Zaretskii
2022-09-14 18:49 ` Karl Fogel
2022-09-14 18:56 ` Eli Zaretskii
2022-09-14 19:15 ` Karl Fogel
2022-09-14 19:21 ` Eli Zaretskii
2022-09-14 19:53 ` Karl Fogel
2022-09-15 6:58 ` Eli Zaretskii
2022-09-15 7:44 ` Stefan Kangas [this message]
2022-09-15 17:59 ` Karl Fogel
2022-09-14 17:39 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2022-09-12 10:13 Stefan Kangas
2022-09-12 11:28 ` Michael Albinus
2022-09-12 11:55 ` Michael Albinus
2022-09-12 11:59 ` Eli Zaretskii
2022-09-12 12:00 ` Eli Zaretskii
2022-09-12 12:03 ` Michael Albinus
2022-09-12 12:20 ` Lars Ingebrigtsen
2022-09-12 20:59 ` Karl Fogel
2022-09-13 1:36 ` Stefan Kangas
2022-09-13 2:30 ` Eli Zaretskii
2022-09-13 9:39 ` Stefan Kangas
2022-09-13 12:03 ` Eli Zaretskii
2022-09-13 12:46 ` Stefan Kangas
2022-09-13 13:03 ` Lars Ingebrigtsen
2022-09-13 13:43 ` Robert Pluim
2022-09-13 13:55 ` Lars Ingebrigtsen
2022-09-14 16:43 ` Stefan Kangas
2022-09-14 16:47 ` Lars Ingebrigtsen
2022-09-14 17:33 ` Eli Zaretskii
2022-09-14 22:50 ` Stefan Kangas
2022-09-15 5:37 ` Eli Zaretskii
2022-09-15 7:44 ` Stefan Kangas
2022-09-14 16:54 ` Eli Zaretskii
2022-09-14 22:50 ` Stefan Kangas
2022-09-15 5:38 ` Eli Zaretskii
2022-09-14 16:57 ` Karl Fogel
2022-09-14 18:34 ` Bob Rogers
2022-09-16 14:56 ` Stefan Kangas
2022-09-13 15:29 ` Karl Fogel
2022-09-13 15:49 ` Eli Zaretskii
2022-09-13 15:52 ` Eli Zaretskii
2022-09-14 16:59 ` Karl Fogel
2022-09-14 17:04 ` 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='CADwFkm=dEMWfNcLjP5ASHvoQg3RFsdsOkxsko7YQFQSws9e8+g@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
/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.