From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: The art of closing bug reports Date: Sun, 10 Jul 2011 02:43:19 -0700 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1310291043 305 80.91.229.12 (10 Jul 2011 09:44:03 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 10 Jul 2011 09:44:03 +0000 (UTC) Cc: 'Juanma Barranquero' , 'Emacs-Devel devel' To: "'Tim Cross'" , "'Lennart Borgman'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 10 11:43:58 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QfqYO-0004ma-PA for ged-emacs-devel@m.gmane.org; Sun, 10 Jul 2011 11:43:56 +0200 Original-Received: from localhost ([::1]:44865 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QfqYO-00083r-3Y for ged-emacs-devel@m.gmane.org; Sun, 10 Jul 2011 05:43:56 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:38660) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QfqY5-00083W-Un for emacs-devel@gnu.org; Sun, 10 Jul 2011 05:43:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QfqY4-0006T4-Uy for emacs-devel@gnu.org; Sun, 10 Jul 2011 05:43:37 -0400 Original-Received: from acsinet15.oracle.com ([141.146.126.227]:54800) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QfqY4-0006Sw-M3 for emacs-devel@gnu.org; Sun, 10 Jul 2011 05:43:36 -0400 Original-Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by acsinet15.oracle.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id p6A9hXHo023605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 10 Jul 2011 09:43:34 GMT Original-Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id p6A9hWaV019170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Jul 2011 09:43:33 GMT Original-Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p6A9hRt9023246; Sun, 10 Jul 2011 04:43:27 -0500 Original-Received: from dradamslap1 (/10.159.32.168) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 10 Jul 2011 02:43:27 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: Acw+wRF+vMa9R3IRS+uvtl71z9UadQAIbG6Q X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A020201.4E197447.0030:SCFMA922111,ss=1,re=-4.000,fgs=0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 1) X-Received-From: 141.146.126.227 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:141893 Archived-At: > 1. Include the full bug report subject and not just the bug number in > the closure notification. I regularly see closure notices that only > include the bug number and a message which often just says the bug has > been closed. 1+ But since this is variable, I've been assuming (?) that this was due to the way some particular bug subjects were created in the first place (e.g. perhaps older bugs). It seems that some have `#9999' in the subject, some have just `9999', some have the complete subject. It is good to have both the subject and `#999' - easiest to run a search. If the bug number were in fact quoted (in future), then a search would be easier still. For example, searching for "`#999'" gives no false positives such as searching for "999" or "#999" can ("#999" as prefix or "999" as substring). (I'm assuming a literal, not a regexp search, which is the case for at least some mail clients. Yes, this is a nit. Just something we might consider, if other things are equal. > The problem with this is that it gives no clue as to which bug it was. > We tend not to remember bug report numbers, but often will recognise > subject or description. Knowing that a particular bug (and I'm talking > about ones that you have not lodged yourself) has been closed can be > very useful.