From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@gmail.com
Cc: 35968@debbugs.gnu.org
Subject: bug#35968: Release 26.3
Date: Wed, 29 May 2019 19:04:56 +0300 [thread overview]
Message-ID: <83r28hxn4n.fsf@gnu.org> (raw)
In-Reply-To: <85h89ecmex.fsf@gmail.com> (npostavs@gmail.com)
> From: npostavs@gmail.com
> Date: Tue, 28 May 2019 17:13:42 -0400
>
> Tracking bugs to fix before releasing Emacs 26.3.
>
> I'm thinking of the following:
>
> #35767 26.1; byte compiler lost warning about calling define-key with wrong number of arguments
> - regression from 25.3, has a simple fix.
> - https://debbugs.gnu.org/35767#8
> #29220 26.0.90; eieio-persistent-read fail to restore saved object.
> - regression from 25.3, reasonably simple partial (conditional on eieio-backward-compatibility) fix.
> - https://debbugs.gnu.org/29220#193
> #35739 [w32] Bad signature from GNU ELPA for archive-contents
> - fixed in master
> - for emacs-26 need something less invasive
> #35770 [PATCH] Broken duplicate case elimination in switch byte-compilation
> - regression from 25.3, fixed in master
> - for emacs-26 just disable optimization (?)
I'm okay with doing everything where we have a simple enough fix,
which means all but the penultimate bug.
Thanks.
next prev parent reply other threads:[~2019-05-29 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 21:13 bug#35968: Release 26.3 npostavs
2019-05-28 22:25 ` Noam Postavsky
2019-05-30 23:07 ` Noam Postavsky
2019-06-06 1:27 ` Noam Postavsky
2019-06-06 2:35 ` Eli Zaretskii
2019-06-11 20:00 ` Nicolas Petton
2019-06-12 2:30 ` Eli Zaretskii
2019-05-29 16:04 ` Eli Zaretskii [this message]
2019-05-30 1:10 ` bug#35968: Proposed clean-compile patches for release 26.3 Paul Eggert
2019-05-30 14:03 ` Eli Zaretskii
2019-05-30 22:30 ` Paul Eggert
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=83r28hxn4n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35968@debbugs.gnu.org \
--cc=npostavs@gmail.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.