From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 29165@debbugs.gnu.org, raeburn@permabit.com,
p.stephani2@gmail.com, schwab@linux-m68k.org,
monnier@iro.umontreal.ca
Subject: bug#29165: 26.0.90; can't use some code byte-compiled under emacs 24
Date: Sun, 21 Jan 2018 20:01:16 +0200 [thread overview]
Message-ID: <83mv17qefn.fsf@gnu.org> (raw)
In-Reply-To: <87k1wbnpit.fsf@users.sourceforge.net> (message from Noam Postavsky on Sun, 21 Jan 2018 11:30:02 -0500)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Cc: rgm@gnu.org, 29165@debbugs.gnu.org, raeburn@permabit.com, p.stephani2@gmail.com, schwab@linux-m68k.org, monnier@iro.umontreal.ca
> Date: Sun, 21 Jan 2018 11:30:02 -0500
>
> > Is it important enough to justify one more pretest, after 26.0.91, and
> > delay the release by a few more weeks? Because that's what would be
> > needed if we install this on the release branch.
>
> Hmm, no, I think these edge cases are not important enough to delay the
> release.
>
> > Besides, this change was introduced more than a year ago, and we did
> > that in clear understanding that it changes behavior. So "closer to
> > Emacs 25" doesn't sound like a convincing argument in this case,
> > because we gave up that similarity up front.
>
> Well, the unfortunate thing about waiting is that we get more strict in
> v26 and then turn around in v27 and (partially) reverse the decision.
> But still, as I said above, not worth delaying the release over it.
OK, then please push to master, and thanks.
next prev parent reply other threads:[~2018-01-21 18:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 6:57 bug#29165: 26.0.90; can't use some code byte-compiled under emacs 24 Ken Raeburn
2017-11-06 12:44 ` Noam Postavsky
2017-11-06 14:24 ` Drew Adams
2017-11-06 14:35 ` Noam Postavsky
2017-11-06 14:40 ` Drew Adams
2017-11-06 17:20 ` Philipp Stephani
2017-11-06 17:25 ` Ken Raeburn
2017-11-06 18:10 ` Andreas Schwab
2017-11-06 19:10 ` Ken Raeburn
2017-11-06 19:16 ` Noam Postavsky
2017-11-13 18:06 ` Noam Postavsky
2017-11-13 19:42 ` Ken Raeburn
2017-11-13 20:05 ` Noam Postavsky
2017-11-27 22:24 ` Noam Postavsky
2017-12-13 22:36 ` Noam Postavsky
2017-12-15 16:48 ` Glenn Morris
2017-12-16 4:54 ` Noam Postavsky
2018-01-20 22:10 ` Noam Postavsky
2018-01-21 3:02 ` Stefan Monnier
2018-01-21 16:04 ` Eli Zaretskii
2018-01-21 16:30 ` Noam Postavsky
2018-01-21 18:01 ` Eli Zaretskii [this message]
2018-03-25 15:32 ` Noam Postavsky
2017-12-13 23:39 ` Stefan Monnier
2017-12-15 1:16 ` Noam Postavsky
2017-12-15 3:04 ` Stefan Monnier
2017-12-15 5:17 ` Ken Raeburn
2017-12-15 13:54 ` Stefan Monnier
2017-11-06 19:31 ` Drew Adams
2017-11-06 16:08 ` 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=83mv17qefn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29165@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.net \
--cc=p.stephani2@gmail.com \
--cc=raeburn@permabit.com \
--cc=schwab@linux-m68k.org \
/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.