From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Don Armstrong Newsgroups: gmane.emacs.devel Subject: Re: Subject of closure notifications sent to submitters [Re: bug#119acknowledged by developer (Closing fixed bugs)] Date: Thu, 12 Jun 2008 10:27:51 -0700 Message-ID: <20080612172751.GP17024@archimedes.ucr.edu> References: <20080612161126.GL15070@volo.donarmstrong.com> <008501c8ccac$1fffd400$c2b22382@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1213291744 9825 80.91.229.12 (12 Jun 2008 17:29:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 12 Jun 2008 17:29:04 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 12 19:29:47 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K6qcL-0001aK-2c for ged-emacs-devel@m.gmane.org; Thu, 12 Jun 2008 19:29:45 +0200 Original-Received: from localhost ([127.0.0.1]:38143 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6qbX-0000Ay-BU for ged-emacs-devel@m.gmane.org; Thu, 12 Jun 2008 13:28:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6qac-0008LS-JB for emacs-devel@gnu.org; Thu, 12 Jun 2008 13:27:58 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6qaa-0008Jr-Tz for emacs-devel@gnu.org; Thu, 12 Jun 2008 13:27:58 -0400 Original-Received: from [199.232.76.173] (port=43989 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6qaa-0008Je-KV for emacs-devel@gnu.org; Thu, 12 Jun 2008 13:27:56 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:45484) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K6qaa-0000hW-7D for emacs-devel@gnu.org; Thu, 12 Jun 2008 13:27:56 -0400 Original-Received: from archimedes.ucr.edu (archimedes.ucr.edu [138.23.92.79]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with SMTP id m5CHRpnV003068 for ; Thu, 12 Jun 2008 10:27:52 -0700 Original-Received: (nullmailer pid 7366 invoked by uid 1000); Thu, 12 Jun 2008 17:27:51 -0000 Mail-Followup-To: emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: <008501c8ccac$1fffd400$c2b22382@us.oracle.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:99025 Archived-At: On Thu, 12 Jun 2008, Drew Adams wrote: > Well, what can I say? Such a subject line is useless to me. The only > connection it shows with the bug I filed is the bug number, and that > is not the most helpful for finding the thread of messages, > including the original, that involve the bug. That's a message which is sent to a submitter, which is outside of the thread of the discussion of the bug in most cases. Furthermore, the message you got sent comes from using close, which is deprecated because it doesn't provide enough information to the submitter to see exactly why their bug was closed. [I'm most likely going to remove it in the future anyway, so people whouldn't get used to using it now.] > FWIW, any bug tracking system I've ever used sends mails that keep > the original bug title intact as the subject. Even when the original > title does not accurately describe the bug, it is kept (along with > the bug number) as the bug identifier, and that identifier is used > in the Subject of all mails concerning the bug. That's because most bug tracking systems don't use mail for everything that they do, and the only subject they have is the original message. > Also, please at least add a link in the mail body to the original > bug report in a threaded list on a Web page. We should be able to > just click a link in any mail regarding a particular bug to get to > the complete thread. It's in the footer of all messages sent out by the BTS (or at last, should be; if it's not, bounce me a complete example off list.) Don Armstrong -- This can't be happening to me. I've got tenure. -- James Hynes _Publish and Perish_ http://www.donarmstrong.com http://rzlab.ucr.edu