From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3033 invoked by alias); 14 Apr 2002 08:02:52 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 2965 invoked from network); 14 Apr 2002 08:02:48 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 14 Apr 2002 08:02:48 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id g3E82j832166; Sun, 14 Apr 2002 03:02:45 -0500 Date: Sun, 14 Apr 2002 01:02:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200204140802.g3E82j832166@duracef.shout.net> To: dberlin@dberlin.org Subject: Re: [patch] gdb.c++/local.exp: add pr numbers Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com X-SW-Source: 2002-04/txt/msg00498.txt.bz2 Daniel Berlin writes: 1. Bugzilla supports multiple products by default, in a single database. (Each product can itself, have multiple components, as well) 2. Bug ids are unique within a given bugzilla database. Ah. Ok. So this covers the case that I care about the most, which is referring to gcc bugs. As far as I know, gcc (broadly speaking, the whole "gnu compiler collection") are the only Free Software compilers supported by gdb. Although maybe my knowledge is limited? > However, this *is* actually going to be annoying in the initial import, > since it means that if they share the same bugzilla system (which only > makes sense), i'll have to remap gdb's bug numbers to a new range (IE > add 10000 to them. There are almost exactly 7000 gcc bug reports, and > not going to be 3000 more before we switch) So gnats bug #277 is going to become bugzilla bug #10277, for instance? Michael C