From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21245 invoked by alias); 22 Sep 2003 02:55:11 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 21238 invoked from network); 22 Sep 2003 02:55:11 -0000 Received: from unknown (HELO dberlin.org) (69.3.5.6) by sources.redhat.com with SMTP; 22 Sep 2003 02:55:11 -0000 Received: from [127.0.0.1] (HELO dberlin.org) by dberlin.org (CommuniGate Pro SMTP 4.1.1) with ESMTP-TLS id 5053203; Sun, 21 Sep 2003 22:55:10 -0400 Date: Mon, 22 Sep 2003 02:55:00 -0000 From: Daniel Berlin To: Jim Blandy cc: Christopher Faylor , gdb@sources.redhat.com Subject: Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3 In-Reply-To: Message-ID: References: <200309192229.h8JMT9q0021832@duracef.shout.net> <20030919235818.GC17343@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-09/txt/msg00261.txt.bz2 On Fri, 19 Sep 2003, Jim Blandy wrote: > Christopher Faylor writes: > > > On Fri, Sep 19, 2003 at 06:29:09PM -0400, Michael Elizabeth Chastain wrote: > > >I think it's good to send the patch to gdb-patches as usual, > > >and then mail to gdb-gnats with a URL that points to the patch. > > >That means you have to for the patch to show up in the gdb-patches > > >archive, but that takes just a few seconds. > > > > Just as an aside, I'm wondering if it is time to consider switching > > to bugzilla. I think bugzilla handles this issue a little better. > > Does bugzilla allow you to CC the bug on E-mail messages, the way > GNATS does? I love that, and I haven't seen bugzilla do it. Uhh, of course. It's even much simpler than the gnats handling code, because it's a simple database operation. The bulk of the code (a couple hundred lines of perl) is devoted to parsing out and handling attachments in the email (while a perl module handles most of the details, we still have to do stuff with the data itself, make up a filename for stupid mailers, etc), as well as verifying permissions and issuing new accounts for new users.