From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14930 invoked by alias); 10 Feb 2003 01:23:34 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 14923 invoked from network); 10 Feb 2003 01:23:34 -0000 Received: from unknown (HELO dberlin.org) (69.3.5.6) by 172.16.49.205 with SMTP; 10 Feb 2003 01:23:34 -0000 Received: from [192.168.1.34] (account dberlin HELO dberlin.org) by dberlin.org (CommuniGate Pro SMTP 4.0.5) with ESMTP-TLS id 2740553; Sun, 09 Feb 2003 20:23:34 -0500 Date: Mon, 10 Feb 2003 01:23:00 -0000 Subject: Re: Web part of bugzilla is ready (fwd) Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: overseers@gcc.gnu.org To: Christopher Faylor From: Daniel Berlin In-Reply-To: <20030208162540.GA8744@redhat.com> Message-Id: <45860843-3C96-11D7-BEA6-000393575BCC@dberlin.org> Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q1/txt/msg00284.txt.bz2 On Saturday, February 8, 2003, at 11:25 AM, Christopher Faylor wrote: > On Fri, Feb 07, 2003 at 11:53:41PM -0500, Daniel Berlin wrote: >> The second is a more general interface, that can do more (IE do bug >> searches, etc, by email). It just needs a new email address. >> This script is done and ready to go, but secondary, so if you are >> busy at >> the moment, don't worry about it. > > This is easy to set up. I just have to create a gcc-bugzilla alias > that > runs this program, similar to the gcc-gnats alias. I'll set up the > alias if you provide the path to the program. Okay, it's ready. The program is /pool/bugzilla/bugzilla-2.17.3/contrib/bugzilla_email.pl It expects to be run with a current working directory of /pool/bugzilla/bugzilla-2.17.3/contrib/, but only because i didn't use absolute paths to tell it where to find files, i used "../". > >>> 2) Something to generate email when a bug is entered in bugzilla. >>> >> This is already done by bugzilla on its own. > > Cool. > >>> Neither is hard to do. I can set up 1 immediately, if you want. We >>> can >>> set up a gcc-bugzilla mailing list and have it go directly into your >>> database. Just tell me what program needs to be run. >> >> I shall, the second i have it done. > > Ok. I just didn't want to leave the impression that it was stalled on > the sysadmin side of things. > Okay, i'm actually happy with all the scripts now, but since they all rely on basically the same perl code to do most of the work, i'd rather start with the non-intrusive one, which is the one i was talking about above (for the gcc-bugzilla email address). > cgf