all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 37260@debbugs.gnu.org
Subject: bug#37260: 26.3; Emacs 26.3 NEWS
Date: Sun, 01 Sep 2019 21:35:29 +0300	[thread overview]
Message-ID: <834l1v985q.fsf@gnu.org> (raw)
In-Reply-To: <a5a2e9f5-fcfa-4656-bc50-b8ccaf706bb4@default> (message from Drew Adams on Sun, 1 Sep 2019 11:25:24 -0700 (PDT))

> Date: Sun, 1 Sep 2019 11:25:24 -0700 (PDT)
> From: Drew Adams <drew.adams@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).





  reply	other threads:[~2019-09-01 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-01 18:25 bug#37260: 26.3; Emacs 26.3 NEWS Drew Adams
2019-09-01 18:35 ` Eli Zaretskii [this message]
2019-09-01 20:20   ` Nicolas Petton
2019-09-02 23:47   ` Glenn Morris

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=834l1v985q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37260@debbugs.gnu.org \
    --cc=drew.adams@oracle.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.