From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: Bug Database? Date: Thu, 19 Oct 2006 09:50:37 +0100 Message-ID: <45373C5D.7070508@gnu.org> References: <17717.20433.183356.106695@kahikatea.snap.net.nz> <87odsameu4.fsf@furball.mit.edu> <17717.45053.900033.152204@kahikatea.snap.net.nz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1161248247 26700 80.91.229.2 (19 Oct 2006 08:57:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 19 Oct 2006 08:57:27 +0000 (UTC) Cc: Juanma Barranquero , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 19 10:57:25 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GaTiJ-0000cB-Gd for ged-emacs-devel@m.gmane.org; Thu, 19 Oct 2006 10:57:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GaTiI-00068W-0g for ged-emacs-devel@m.gmane.org; Thu, 19 Oct 2006 04:57:18 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GaTcs-0004Uj-35 for emacs-devel@gnu.org; Thu, 19 Oct 2006 04:51:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GaTcp-0004Tp-UF for emacs-devel@gnu.org; Thu, 19 Oct 2006 04:51:41 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GaTco-0004T6-Hr for emacs-devel@gnu.org; Thu, 19 Oct 2006 04:51:38 -0400 Original-Received: from [213.86.207.50] (helo=exchange.integrasp.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GaTcm-0002Nu-F3; Thu, 19 Oct 2006 04:51:36 -0400 Original-Received: from [192.168.111.61] (localhost [127.0.0.1]) by exchange.integrasp.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id TPPWTALQ; Thu, 19 Oct 2006 09:41:46 +0100 Original-Received: from 192.168.111.61 ([192.168.111.61] helo=[192.168.111.61]) by ASSP-nospam; 19 Oct 2006 09:41:46 +0100 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666 Original-To: rms@gnu.org In-Reply-To: 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:60911 Archived-At: Richard Stallman wrote: > If we are to run a bug tracker, we first need to work out a plan for > entering bugs reported by email into the data base. We need to find a > person or persons who will do the work. > It seems like the sort of job that could easily be automated by a script. In fact, my preference would be to have the script be the only recipient of the emacs-pretest-bug and bug-emacs mail aliases, and to create the entry in the bug database, then add the bug id into the email before forwarding it to the mailing list subscribers. Things like prioritizing and categorizing would still have to be done by hand, but at least there is a guarantee that all bugs make it into the database. Spam might be a problem with that approach, so perhaps only automatically add bugs that are in the format created by report-emacs-bug, and forward incorrectly formatted emails directly to the list for manual addition.