GNU bug report logs -
#37260
26.3; Emacs 26.3 NEWS
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Sun, 1 Sep 2019 18:27:01 UTC
Severity: minor
Tags: notabug
Found in version 26.3
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37260 in the body.
You can then email your comments to 37260 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37260
; Package
emacs
.
(Sun, 01 Sep 2019 18:27:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 01 Sep 2019 18:27:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
NEWS for Emacs 26.3 looks quite empty. I don't think I've ever
seen this kind of NEWS for a release before, but perhaps I just
haven't noticed it.
There are 8 empty sections (just titles, no content), and only one
non-empty section, which has only this:
* Changes in Emacs 26.3
** New option 'help-enable-completion-auto-load'.
This allows disabling the new feature introduced in Emacs 26.1 which
loads files during completion of 'C-h f' and 'C-h v' according to
'definition-prefixes'.
** Emacs now supports the new Japanese Era name.
The newly assigned codepoint U+32FF was added to the Unicode Character
Database compiled into Emacs.
1. Is this correct, or is something missing? If correct, shouldn't
there perhaps be some indication of _why_ a new release was created just
for those two changes? On the face of it, they don't seem very
consequential. Is there something more to it than what there appears to
be?
2. Is it normal that we have empty sections? Shouldn't we explicitly
note that there are no changes of each of those kinds? E.g., why have
an empty section for "Installation Changes in Emacs 26.3, if there are
none? Or why not have the section, but with some content (e.g. "None.")
that indicates that there are no installation changes?
In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
of 2019-08-29
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor `Microsoft Corp.', version 10.0.17763
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37260
; Package
emacs
.
(Sun, 01 Sep 2019 18:36:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 37260 <at> debbugs.gnu.org (full text, mbox):
> Date: Sun, 1 Sep 2019 11:25:24 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
>
> NEWS for Emacs 26.3 looks quite empty. I don't think I've ever
> seen this kind of NEWS for a release before, but perhaps I just
> haven't noticed it.
It's a bugfix release, so ideally there should be no NEWS-worthy
changes at all.
> There are 8 empty sections (just titles, no content), and only one
> non-empty section, which has only this:
>
> * Changes in Emacs 26.3
>
> ** New option 'help-enable-completion-auto-load'.
> This allows disabling the new feature introduced in Emacs 26.1 which
> loads files during completion of 'C-h f' and 'C-h v' according to
> 'definition-prefixes'.
>
> ** Emacs now supports the new Japanese Era name.
> The newly assigned codepoint U+32FF was added to the Unicode Character
> Database compiled into Emacs.
>
> 1. Is this correct, or is something missing?
Nothing's missing, AFAIK.
> 2. Is it normal that we have empty sections?
It's an artifact of converting an RC (where empty sections are
acceptable) to a release (where they shouldn't be).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37260
; Package
emacs
.
(Sun, 01 Sep 2019 20:21:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 37260 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Eli Zaretskii <eliz <at> gnu.org> writes:
>> 2. Is it normal that we have empty sections?
>
> It's an artifact of converting an RC (where empty sections are
> acceptable) to a release (where they shouldn't be).
Maybe next time we make a tarball for a RC of a bugfix release, we
should remove all empty sections (thus only allow empty sections in
pretest tarballs).
Cheers,
Nico
[signature.asc (application/pgp-signature, inline)]
Reply sent
to
Glenn Morris <rgm <at> gnu.org>
:
You have taken responsibility.
(Mon, 02 Sep 2019 23:48:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Drew Adams <drew.adams <at> oracle.com>
:
bug acknowledged by developer.
(Mon, 02 Sep 2019 23:48:04 GMT)
Full text and
rfc822 format available.
Message #16 received at 37260-done <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii wrote:
> It's an artifact of converting an RC (where empty sections are
> acceptable) to a release (where they shouldn't be).
An RC is supposed to be literally identical to a release.
Anyway, it had already been fixed in the repository.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 01 Oct 2019 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 261 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.