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: Recentish C-s M-y change Date: Sat, 02 Jan 2021 09:15:04 +0200 Message-ID: <837dovg687.fsf@gnu.org> References: <<87r1na4tyu.fsf@gnus.org>> <<87tus6tj7s.fsf@mail.linkov.net>> <<87a6txigm1.fsf@gnus.org>> <<874kk5lzew.fsf@mail.linkov.net>> <> <<87eej8ifll.fsf@mail.linkov.net>> <> <<87h7o3k5b5.fsf@mail.linkov.net>> <> <> <83wnwwg8iu.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26477"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ams@gnu.org, juri@linkov.net, larsi@gnus.org, drew.adams@oracle.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 02 08:16:39 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 1kvb9T-0006lN-Cv for ged-emacs-devel@m.gmane-mx.org; Sat, 02 Jan 2021 08:16:39 +0100 Original-Received: from localhost ([::1]:50088 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kvb9S-0001fx-Fd for ged-emacs-devel@m.gmane-mx.org; Sat, 02 Jan 2021 02:16:38 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45566) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kvb8X-000177-Rj for emacs-devel@gnu.org; Sat, 02 Jan 2021 02:15:41 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48808) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kvb8W-0006vE-Ig; Sat, 02 Jan 2021 02:15:40 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2240 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kvb8A-00066x-PP; Sat, 02 Jan 2021 02:15:19 -0500 In-Reply-To: (message from Richard Stallman on Sat, 02 Jan 2021 00:34:04 -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:262295 Archived-At: > From: Richard Stallman > Cc: ams@gnu.org, larsi@gnus.org, emacs-devel@gnu.org, > drew.adams@oracle.com, juri@linkov.net > Date: Sat, 02 Jan 2021 00:34:04 -0500 > > I probably won't read a thread that discusses how to fix a bug. > I would not expect a decision about a change in features to be > made in such a thread. That expectation is incorrect, both factually and in principle. People tend to continue a discussion thread even when it wanders far away of the original topic or issue. Calls to change the Subject when that happens have only very limited success. Such is life. > Thus I propose a rule, which I hope people will remember to apply, > that if a change in features has been discussed inside a thread > about a specific bug, always to raise the issue on emacs-devel > afterward. As a guideline, I could agree. But as an enforced rule, I don't think this will fly, and I don't think we should waste our limited resources to try enforcing it.