unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 27.1 released
Date: Wed, 12 Aug 2020 22:21:09 +0300	[thread overview]
Message-ID: <83y2mjn00q.fsf@gnu.org> (raw)
In-Reply-To: <E1CA79CA-6C2D-475F-848A-D55FCAFC9988@acm.org> (message from Mattias Engdegård on Wed, 12 Aug 2020 21:07:05 +0200)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Wed, 12 Aug 2020 21:07:05 +0200
> Cc: emacs-devel@gnu.org
> 
> > How easily would people bump into this in real-life use cases?  I
> > think the answer to that will tell how important is it to fix it in
> > Emacs 27.
> 
> We have no idea. Most bugs are never reported; people blame themselves and try a different approach, or just blame Emacs in general. That's why it's important to fix bugs we find even absent any concrete evidence that it has affected anyone else.

That kind of abstract arguments don't help.  So I'm left to my own
devices, and therefore please leave this change on master.

> >>> I'm uneasy with this, as it would indirectly affect many functions.
> >> 
> >> Which many functions did you have in mind?
> > 
> > Its callers inside Calc.  Suppose there's some subtle issue with the
> > change, or some unintended consequence.
> 
> Mind being more specific?

I just counted its callers, that's all.  A change in a function that
has many callers could have unintended consequences beyond the
function itself.

> >  OTOH, how probable is it to have a negative x here?
> 
> The post-hoc probability is 1 because a user was affected by and reported the bug, but that's not the point: the erroneous simplification GCD(x, 0) -> x leads to trouble later on, as the report shows.

I thought you were going to help me make a better decision, but I
guess I was too naïve.  Please leave this one on master as well.



  reply	other threads:[~2020-08-12 19:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 23:00 Emacs 27.1 released Nicolas Petton
2020-08-10 23:52 ` Stefan Kangas
2020-08-12  2:24   ` Richard Stallman
2020-08-12 14:05     ` Noam Postavsky
2020-08-24 14:25   ` Stefan Kangas
2020-08-24 14:30     ` Lars Ingebrigtsen
2020-08-24 14:56       ` Drew Adams
2020-08-11  0:50 ` Mingde (Matthew) Zeng
2020-08-11  2:59 ` 황병희
2020-08-11  4:24 ` Jay Sulzberger
2020-08-11  8:19 ` Ulrich Mueller
2020-08-11 18:25   ` Eli Zaretskii
2020-08-12  8:09     ` Michael Albinus
2020-08-12 13:48       ` Phil Sainty
2020-08-12 14:21       ` Eli Zaretskii
2020-08-12 16:20         ` Mattias Engdegård
2020-08-12 16:33           ` Robert Pluim
2020-08-12 16:47           ` Eli Zaretskii
2020-08-12 18:01             ` Mattias Engdegård
2020-08-12 18:27               ` Eli Zaretskii
2020-08-12 19:07                 ` Mattias Engdegård
2020-08-12 19:21                   ` Eli Zaretskii [this message]
2020-08-13 19:50                     ` Mattias Engdegård
2020-08-14  6:02                       ` Eli Zaretskii
2020-08-14 12:51                         ` Mattias Engdegård
2020-08-14 13:28                           ` Eli Zaretskii
2020-08-16  8:19                             ` Mattias Engdegård
2020-08-13 14:34         ` Michael Albinus
2020-08-12 12:01 ` phillip.lord
2020-08-15 17:49   ` Emacs 27.1 Windows Binaries -- testing wanted phillip.lord
2020-08-15 17:54     ` Eli Zaretskii
2020-08-15 18:38     ` Stephen Leake
2020-08-15 19:57     ` Alan Third
2020-08-17  4:44     ` Sivaram Neelakantan
2020-08-17  5:40     ` 范凯
2020-08-17 23:24     ` Emacs " Tak Kunihiro

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y2mjn00q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).