From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: Unanswered Emacs Problem Reports 40+ Months Date: Fri, 25 Oct 2013 14:47:35 -0400 Message-ID: References: <52689833.7060109@gnulinuxlibre.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1382726857 27604 80.91.229.3 (25 Oct 2013 18:47:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Oct 2013 18:47:37 +0000 (UTC) Cc: Christian Bryant , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 25 20:47:42 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VZmQA-0000z0-5l for ged-emacs-devel@m.gmane.org; Fri, 25 Oct 2013 20:47:42 +0200 Original-Received: from localhost ([::1]:60442 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZmQ9-0004eB-On for ged-emacs-devel@m.gmane.org; Fri, 25 Oct 2013 14:47:41 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35219) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZmQ6-0004e4-S2 for emacs-devel@gnu.org; Fri, 25 Oct 2013 14:47:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VZmQ5-0007Vb-RC for emacs-devel@gnu.org; Fri, 25 Oct 2013 14:47:38 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60261) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZmQ5-0007VL-Nf for emacs-devel@gnu.org; Fri, 25 Oct 2013 14:47:37 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1VZmQ4-0007WV-54; Fri, 25 Oct 2013 14:47:36 -0400 X-Spook: tempest pre-emptive eavesdropping government cypherpunk X-Ran: a&4jOejEYwyBz\K:r3u2m)x)h"Y]EcSYhWi%`1[-;)RJ!h-y/T (Stefan Monnier's message of "Thu, 24 Oct 2013 10:21:51 -0400") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:164543 Archived-At: Stefan Monnier wrote: > We're not talking about closing the bugs, but confirming that the bug is > still relevant. Tho, in the absence of a reply by the bug-submitter > within a month (say), we could also decide to close the bug. I imagine most responses will be of two kinds: 1) No reply. Then what? 2) A slightly annoyed "yes, of course my wishlist/doc bug/whatever" still applies, didn't you read it/test it/try my patch?". The useful replies I expect to be a small minority ("It was fixed in 24.1", "I misunderstood and this is not actually a bug", etc.) So I expect the result will be mostly be to annoy the bug reporters. > The idea is to ask the bug-submitter's help. Well, ok. > I think this classification can be made automatically/heuristically > by checking if the last message was from a developer. I'm not optimistic that an automatic process can tell us much, but I guess we'll see.