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: Unable to close a bug in the tracker. Date: Wed, 13 Jan 2010 20:19:38 -0500 Message-ID: References: <87iqb5o7ie.fsf@red-bean.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1263432011 6780 80.91.229.12 (14 Jan 2010 01:20:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 14 Jan 2010 01:20:11 +0000 (UTC) Cc: emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 14 02:20:04 2010 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 1NVENX-0001W4-LA for ged-emacs-devel@m.gmane.org; Thu, 14 Jan 2010 02:20:03 +0100 Original-Received: from localhost ([127.0.0.1]:53861 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVENY-0005Sg-BW for ged-emacs-devel@m.gmane.org; Wed, 13 Jan 2010 20:20:04 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NVENC-00059r-O4 for emacs-devel@gnu.org; Wed, 13 Jan 2010 20:19:42 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NVEN9-00054l-4h for emacs-devel@gnu.org; Wed, 13 Jan 2010 20:19:42 -0500 Original-Received: from [199.232.76.173] (port=33063 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVEN8-00054b-NK for emacs-devel@gnu.org; Wed, 13 Jan 2010 20:19:38 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:35773) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NVEN8-0007ef-Et for emacs-devel@gnu.org; Wed, 13 Jan 2010 20:19:38 -0500 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1NVEN8-0000Fn-7B; Wed, 13 Jan 2010 20:19:38 -0500 X-Spook: Adriatic USCOI Juiliett Class Submarine asset enigma X-Ran: Qy`|+\(*]NOB@40=~O#d(+)tv~n.3`9%5v"D}7blO#/NQc," (Karl Fogel's message of "Wed, 13 Jan 2010 19:27:37 -0500") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-operating-system: by monty-python.gnu.org: GNU/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:119952 Archived-At: Karl Fogel wrote: > For a project like Emacs, a bug tracker whose primary interface is > email is borderline useless. When we were searching for a bug tracker, one whose primary interface was email was one of main criteria, if not the main issue. > * What is "Toggle useless messages" for? > (Please don't answer that. I don't care what the answer is; It's easy to remove this button from the display, but it's sometimes useful, and does not seem that big of a deal. > * Why would I want to "View this report as an [mbox folder], > [status mbox], [maintainer mbox]"? Who is this aimed at? People who want to download the raw report. > * Why does the bug report *start* by default with "Message #3"? Because of the useless messages which you don't care about, I think. > * Why does the bottom of the bug report say "Last modified: Wed Jan 13 > 23:51:14 2010", when the most recent visible activity in the bug > dates from 6 October 2009? It's the date the page was generated. It's a bit useless I agree. > * "To reply or subscribe to this bug, see [here]." This used to be a mailto link, but I changed it in an effort to stop the tide of spam. > 3) Although the web UI could, in theory, give instructions on how to > change the state of the bug, in practice it doesn't. We've had numerous explanations on this list, and I have tried to write notes in admin/notes/bugtracker. Once you get used to it, it's fairly straightforward, I think. > 4) If you're not subscribed to a bug via email, then manipulating > it by email involves lots of cutting-and-pasting from browser to > mail client (i.e., bug number, bug subject, etc). Or you can use those "mbox" buttons to download a mail to which you can then reply.