From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: wait_reading_process_ouput hangs in certain cases (w/ patches) Date: Wed, 14 Mar 2018 18:52:52 -0400 Message-ID: References: <709614e8-1937-07c1-f554-b453ed4f3d4a@binary-island.eu> <7550438b-9fd4-d374-e571-8bb16456cad5@cs.ucla.edu> <797d0e16-1bae-50c2-35f8-05489ffce935@binary-island.eu> <83tvugdiu5.fsf@gnu.org> <877er5s0xv.fsf@gmail.com> <4e4c72bb-295d-81e1-e4ed-cad256bca83c@binary-island.eu> <87zi3v9461.fsf@gmail.com> <87k1uy8x68.fsf@gmail.com> <6d1970af-8c5c-20ba-be09-0b9aa757d663@binary-island.eu> <13b3e003-d12b-33a7-3ebe-c07b017a7cc0@binary-island.eu> <833714rm3d.fsf@gnu.org> <7b64afc3-e9b0-536d-1e42-a5f5d74f1adf@binary-island.eu> <2563fb58-4d85-3518-d8fc-a5cdc70c704e@binary-island.eu> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1521067881 15472 195.159.176.226 (14 Mar 2018 22:51:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 14 Mar 2018 22:51:21 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 14 23:51:17 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ewFEq-0003v3-Se for ged-emacs-devel@m.gmane.org; Wed, 14 Mar 2018 23:51:16 +0100 Original-Received: from localhost ([::1]:48976 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ewFGt-0008PT-Um for ged-emacs-devel@m.gmane.org; Wed, 14 Mar 2018 18:53:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47158) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ewFGc-0008P6-Co for emacs-devel@gnu.org; Wed, 14 Mar 2018 18:53:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ewFGZ-0003Y9-70 for emacs-devel@gnu.org; Wed, 14 Mar 2018 18:53:06 -0400 Original-Received: from [195.159.176.226] (port=56880 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ewFGY-0003Wh-WE for emacs-devel@gnu.org; Wed, 14 Mar 2018 18:53:03 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1ewFEQ-0003TQ-Kz for emacs-devel@gnu.org; Wed, 14 Mar 2018 23:50:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 33 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:G1jLMxqeXHF3fCYcAMaIeaMJhAk= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:223731 Archived-At: > Please excuse my bluntness (not meant as an offense or anything alike) > but that argument does not really hold up. Imagine we were working on a > filesystem, found a longstanding corruption bug that could randomly hit > everyone and silently corrupt data every once in a while (or never). It > gets discovered, fixes are ready but those won't get committed since > the bug has been around for ages, so it can wait a bit longer until the > fixes have been through another timely major release cycle. AFAIK we're talking a bout hangs (and hangs you can interrupt with C-g AFAICT), not about data corruption, so the comparison is unfair. > I still think fixing actual bugs is more important than holding those > fixes back for longer due to the off-chance of introducing new ones. > And again: Isn't that what beta release are for? Finding bugs and fixing > them before the actual stable release? They're for finding&fixing *regressions*, and I think this bug doesn't fall into that category. > I'm not arguing for rushing those fixes out in a 25.3.x release or > whatever. But the 26 beta cycle seems more than appropriate to me as > its a new major release... just my 2ct. My recommendation is based on the premise that 26.1 is due Real Soon Now (with at most one more pretest before the release-candidate). > And I promise I will shut up now about this if nobody agrees with me. :) I don't fundamentally disagree: it's a balancing act. Stefan