From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Confused by y-or-n-p Date: Thu, 07 Jan 2021 16:18:23 +0200 Message-ID: <83o8i0ltjk.fsf@gnu.org> References: <834kkcr1eo.fsf@gnu.org> <83bleinmse.fsf@gnu.org> <56435592-d2d0-5fb6-977f-01e1931da835@gmx.at> <87k0t38g1z.fsf@mail.linkov.net> <83czyvkts6.fsf@gnu.org> <87bleetirr.fsf@mail.linkov.net> <87y2hhri3n.fsf@mail.linkov.net> <83pn2tkfg8.fsf@gnu.org> <871rf7ippu.fsf@mail.linkov.net> <83a6trg6mc.fsf@gnu.org> <87im8f951f.fsf@gnus.org> <83lfdacapo.fsf@gnu.org> <87im8d6q4q.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12836"; mail-complaints-to="usenet@ciao.gmane.io" Cc: juri@linkov.net, rudalics@gmx.at, monnier@iro.umontreal.ca, larsi@gnus.org, emacs-devel@gnu.org, drew.adams@oracle.com To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 07 15:21:25 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kxWAF-0002v5-Bd for ged-emacs-devel@m.gmane-mx.org; Thu, 07 Jan 2021 15:21:23 +0100 Original-Received: from localhost ([::1]:59146 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kxWAE-0003Ao-Dx for ged-emacs-devel@m.gmane-mx.org; Thu, 07 Jan 2021 09:21:22 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48926) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kxW7f-0001DK-3k for emacs-devel@gnu.org; Thu, 07 Jan 2021 09:18:44 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56211) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kxW7a-000721-RC; Thu, 07 Jan 2021 09:18:40 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2989 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kxW7K-0003Zo-Pp; Thu, 07 Jan 2021 09:18:23 -0500 In-Reply-To: (message from Richard Stallman on Thu, 07 Jan 2021 02:33:42 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:262677 Archived-At: > From: Richard Stallman > Cc: larsi@gnus.org, rudalics@gmx.at, eliz@gnu.org, > emacs-devel@gnu.org, drew.adams@oracle.com, juri@linkov.net > Date: Thu, 07 Jan 2021 02:33:42 -0500 > > > Maybe there is no discussion *prior* to the change, but if the change > > ends up being controversial, there is pretty much always a discussion > > (long) before the next release. > > Not always. We just had a case where there wasn't. We will never be able to avoid such incidents in all cases. We are just people, and people make mistakes. It is wrong to try to achieve such unrealistic goals. > I am simply trying to ensure that the discussion will happen before > the next release. We cannot ensure it; see above. We can (and should) try lowering the probability of the discussion not happening, but the measures taken to that end should be on par with the frequency of those incidents. Heavy measures to fix very low-frequency incidents are unjustified, and will harm development for reasons that are not good enough to justify the harm.