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: followup to bug report not included in bug tracker; diverse automatic Subject lines; ACK noise Date: Wed, 18 Jun 2008 12:21:34 -0700 Message-ID: <20080618192134.GA20708@rzlab.ucr.edu> References: <001901c8d112$df848680$0200a8c0@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 1213816916 26062 80.91.229.12 (18 Jun 2008 19:21:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 18 Jun 2008 19:21:56 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 18 21:22:39 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 1K93Er-0001KR-KO for ged-emacs-devel@m.gmane.org; Wed, 18 Jun 2008 21:22:37 +0200 Original-Received: from localhost ([127.0.0.1]:35167 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K93E3-0005gM-2h for ged-emacs-devel@m.gmane.org; Wed, 18 Jun 2008 15:21:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K93Dy-0005ff-Ao for emacs-devel@gnu.org; Wed, 18 Jun 2008 15:21:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K93Dx-0005f4-Lm for emacs-devel@gnu.org; Wed, 18 Jun 2008 15:21:41 -0400 Original-Received: from [199.232.76.173] (port=34486 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K93Dx-0005eV-9L for emacs-devel@gnu.org; Wed, 18 Jun 2008 15:21:41 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:50455) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K93Dw-00069Z-JS for emacs-devel@gnu.org; Wed, 18 Jun 2008 15:21:40 -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 m5IJLYwx024491 for ; Wed, 18 Jun 2008 12:21:35 -0700 Original-Received: (nullmailer pid 13327 invoked by uid 1000); Wed, 18 Jun 2008 19:21:34 -0000 Mail-Followup-To: emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: <001901c8d112$df848680$0200a8c0@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:99412 Archived-At: On Wed, 18 Jun 2008, Drew Adams wrote: > Why can't one just reply to the original thread that reported the > bug? You can. > Why change the thread - subject line and email address, so the > result is multiple email threads for the same bug? You don't have to. > I now have to use search to find matches for keywords ("foo") in the > Subject. Why? If people just use reply, it'll be in the same thread. If they don't, it won't currently, but there's a wishlist bug open to automatically join it to the thread. > If you want to refer to the bug as bug #99 or attach the release > info 23.0.60 to it, why not do that in the message body? There needs to be some way of knowing which bug you're talking about. Normally with debbugs this is done using nnn@emacsbugs.donarmstrong.com mailing address. However, because emacs has been using mailing lists to track bugs for a long time, the decision was made to use the existing code in debbugs which is capable of associating a mail with a specific bug based on the subject. MUAs generally keep the subject intact, and the beginning of the subject is the part that's least likely to be munged by anything, save adding Re: or similar. Finally emailing bugs-gnu-emacs@ or nnn@emacsbugs.d.c is exactly the same for bugs that are in emacs. It's possible that this was the wrong decision, and we should disable entirely messages sent directly to the mailing list, but that's how it's set up now. > Or, if you really must change the Subject line, append instead of > prepend the extra identifying info. The wishlist bug for automagic threading will resolve this; see above. [And in any event, all messages that actually go through the bug tracker will have the same leading bits of the subject anyway, so they should sort together.] > There seems to be no such thing as a (single) thread for a given bug > anymore. And that's not to mention all of the generated ACK messages > that constitute essentially noise. Pretty silly. You can ditch the ack messages by adding "X-Debbugs-No-Ack: yes" or similar to your headers; the ack messages are on by default primarily for casual users. Don Armstrong -- "There's nothing remarkable about it. All one has to do is hit the right keys at the right time and the instrument plays itself." -- Bach http://www.donarmstrong.com http://rzlab.ucr.edu