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: TODO item: obsolete bug-reporting commands Date: Thu, 28 Feb 2008 14:24:35 -0500 Message-ID: References: <87y7962obp.fsf@rabkins.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1204226743 15051 80.91.229.12 (28 Feb 2008 19:25:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 28 Feb 2008 19:25:43 +0000 (UTC) Cc: emacs-devel@gnu.org To: Yoni Rabkin Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 28 20:26:07 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 1JUoO7-0008EM-Fn for ged-emacs-devel@m.gmane.org; Thu, 28 Feb 2008 20:25:51 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUoNb-0007Ab-2j for ged-emacs-devel@m.gmane.org; Thu, 28 Feb 2008 14:25:19 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JUoMx-0006Z3-Cv for emacs-devel@gnu.org; Thu, 28 Feb 2008 14:24:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JUoMv-0006XA-OD for emacs-devel@gnu.org; Thu, 28 Feb 2008 14:24:38 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUoMv-0006Wx-DH for emacs-devel@gnu.org; Thu, 28 Feb 2008 14:24:37 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JUoMv-00054s-3m for emacs-devel@gnu.org; Thu, 28 Feb 2008 14:24:37 -0500 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1JUoMt-0003IM-M6; Thu, 28 Feb 2008 14:24:35 -0500 X-Spook: number key spy CIDA morse Fortezza radar Area 51 Crypto AG X-Ran: av5U>g+:#v~]CLZoCyX8O\$qS1dQeb5[;1(iI1=SkDSXtXoak}J{Y7pX$k.bS/g0 X-Hue: cyan X-Attribution: GM User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:90763 Archived-At: Yoni Rabkin wrote: > The TODO file says: "Check for any included packages that define > obsolete bug-reporting commands. Change them to use report-emacs-bug." I think I added that. All I had in mind was, some packages (eg supercite.el) still directed bug reports to somewhere else, even though they had not been developed outside of Emacs for a long time. It's good to find those and update them to send bug reports to the normal Emacs address. On the other hand, some packages (eg calc) have active maintainers, and if they want to receive bug reports somewhere else, that's their prerogative. So it can't be a blanket replace, it needs checking with the package maintainers. Or perhaps this policy will change if and when a bug database comes into use. So the short answer is that it's probably best to wait and see what happens with the current debbugs experiment before doing much about this. > What is the difference between reporter.el and emacsbug.el (the > emacs-devel archives seem to be silent on reporter.el)? AFAIK, one is a general bug-reporting mechanism, the other is specifically for Emacs. > 1. Should Emacs packages which use reporter.el be converted to using > emacsbug.el and reporter.el retired? No to the last part. Perhaps to the first part. If the bug reports are going to the standard emacs list, it's good to use emacsbug, since it has more bells and whistles. However reporter allows for optional specification of a variable list, which some packages use. Perhaps an optional argument could be added to report-emacs-bug to insert a list of variables and their values. > 2. Should report-emacs-bug be called using > `define-obsolete-function-alias' or `defalias'? I would say d-o-f-a, so that things can one day be further simplified. Eg sc-submit-bug-report can just go away one day. > 3. Should (2) be autoload-ed? I think in general it's reasonable to expect people to load a package before trying to report a bug in it, so no.