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:41:34 -0500 Message-ID: References: <87iqb5o7ie.fsf@red-bean.com> <87d41dmq3o.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 1263433978 11321 80.91.229.12 (14 Jan 2010 01:52:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 14 Jan 2010 01:52:58 +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:52:51 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 1NVEtG-0007qw-PV for ged-emacs-devel@m.gmane.org; Thu, 14 Jan 2010 02:52:51 +0100 Original-Received: from localhost ([127.0.0.1]:59443 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVEtG-0001ly-Vo for ged-emacs-devel@m.gmane.org; Wed, 13 Jan 2010 20:52:50 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NVEt2-0001fh-6l for emacs-devel@gnu.org; Wed, 13 Jan 2010 20:52:37 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NVEsj-0001Ta-Ih for emacs-devel@gnu.org; Wed, 13 Jan 2010 20:52:31 -0500 Original-Received: from [199.232.76.173] (port=50337 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVEsh-0001Sz-Or for emacs-devel@gnu.org; Wed, 13 Jan 2010 20:52:15 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:47886) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NVEsg-0001Bz-P6 for emacs-devel@gnu.org; Wed, 13 Jan 2010 20:52:15 -0500 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1NVEiN-00018Y-5Y; Wed, 13 Jan 2010 20:41:35 -0500 X-Spook: secure Operation Iraqi Freedom Firewalls Defcon CIDA Reno X-Ran: %,4h^V9.Z$:Ypf/^4:mzx(t)gqJ/E`fg+C$Fn1b5ENS+RL,550t6$I_2dt<1k*q/uAsO}] X-Hue: black X-Attribution: GM In-Reply-To: <87d41dmq3o.fsf@red-bean.com> (Karl Fogel's message of "Wed, 13 Jan 2010 20:28:59 -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:119958 Archived-At: Karl Fogel wrote: > I never have to read the documentation for other bug trackers I use, > because it's obvious how to use them. If that doesn't seem like a major > win to you, I'm not sure what else to say... :-). I think it may be a cultural difference. Emacs bugs have always been reported and discussed by email. All the tracker really does is hook that up to a database so that things don't get forgotten about. All the submitter has to do is use M-x report-emacs-bug. This initiates an email exchange with the developers. The submitter doesn't need to know any of the details about the tracker. Only the developers are really expected to close and tag things (though if others want to, that's fine). It does require a bit of an investment to figure out how it works. I think developers are expected to subscribe to bug-gnu-emacs and keep an eye out for bugs that are relevant to them. Browsing bugs on the web and clicking on them to add comments isn't really what it was designed for. I'm certainly not debbugs #1 fan, but now that we've finally been able to tweak it a bit, I'm fairly happy with it.