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: bug#25: Acknowledgement (frame parameter menu-bar-lines changes height of frame) Date: Fri, 29 Feb 2008 08:06:13 -0800 Message-ID: <004001c87aed$0295aae0$0600a8c0@us.oracle.com> References: <003301c87ae6$b2175740$0600a8c0@us.oracle.com> <47C8288D.3050406@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1204301239 26188 80.91.229.12 (29 Feb 2008 16:07:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Feb 2008 16:07:19 +0000 (UTC) Cc: emacs-devel@gnu.org To: "'Jason Rumney'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 29 17:07:44 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 1JV7lh-0007y5-GM for ged-emacs-devel@m.gmane.org; Fri, 29 Feb 2008 17:07:29 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JV7lB-0006U6-3a for ged-emacs-devel@m.gmane.org; Fri, 29 Feb 2008 11:06:57 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JV7l5-0006TT-Ra for emacs-devel@gnu.org; Fri, 29 Feb 2008 11:06:51 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JV7l3-0006SW-Qd for emacs-devel@gnu.org; Fri, 29 Feb 2008 11:06:51 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JV7l3-0006SQ-Jm for emacs-devel@gnu.org; Fri, 29 Feb 2008 11:06:49 -0500 Original-Received: from agminet01.oracle.com ([141.146.126.228]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JV7kz-0001EA-0B; Fri, 29 Feb 2008 11:06:45 -0500 Original-Received: from agmgw2.us.oracle.com (agmgw2.us.oracle.com [152.68.180.213]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id m1TG6diU012209; Fri, 29 Feb 2008 10:06:40 -0600 Original-Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m1TDHrvO012897; Fri, 29 Feb 2008 09:06:39 -0700 Original-Received: from inet-141-146-46-1.oracle.com by acsmt351.oracle.com with ESMTP id 3595638701204301197; Fri, 29 Feb 2008 08:06:37 -0800 Original-Received: from dradamslap1 (/141.144.80.6) by bhmail.oracle.com (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 29 Feb 2008 08:06:37 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <47C8288D.3050406@gnu.org> Thread-Index: Ach66iHqBj32/yATQV+sMYUz3TYglgAAd68g X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 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:90895 Archived-At: > > Uh, why are we getting such emails? > > You are getting this because I picked one of your outstanding > reports to test the bug submission process. I didn't realise > that it would result in an auto-reply to you, next time I > will forward an email from my own address rather than > resending an existing report with original headers intact. OK. No problem. Thanks for the prompt explanation. > > And why does it say to submit further info about the bug to > > "25@emacsbugs.donarmstrong.com, as before." As before? > > Obviously there are problems to be ironed out. HTH. > > We should continue to be able to sort mails by thread, > > sender, etc. in our mail clients, and not have a thread > > get split into different subjects, addresses, etc. > > I think we're going to have to put up with some breakage of > this ideal while we make the transition to the new bug > reporting system. OK (for the transition). > Once the new system is up and running, the prefixes on the > subject line should be consistent once the bug has hit the > system. Consistent is good. Even better is to treat it as a normal mail thread, so the original message is also in the same stream. IOW, bug sending should also have the same prefix, whatever it is. > If we impose requirements like "no changing the subject line" > on bug reporting tools, we are going to end up with a bug > tracker that is basically an unsorted mailing list > archive that someone needs to go in and fix up by hand. I don't see why. Why would an automatic system not be able to keep the subject intact (using whatever prefixing convention it wants, consistently). I use bug trackers everyday, as I'm sure others do also. I have no problem with a Web-based system, with or without initial reporting by email. But there should be one-stop shopping for the complete bug-report history: everything should be in one thread - either email or on a Web page, and that one place should also be where you post updates. It should be easy to sort and search bug reports in different ways. This is nothing new, in general.