From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32334 invoked by alias); 27 Jun 2005 12:45:29 -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 32323 invoked by uid 22791); 27 Jun 2005 12:45:25 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 27 Jun 2005 12:45:25 +0000 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1DmszL-0002ad-Fi; Mon, 27 Jun 2005 08:45:23 -0400 Date: Mon, 27 Jun 2005 12:45:00 -0000 From: Daniel Jacobowitz To: Wu Zhou Cc: gdb@sources.redhat.com Subject: Re: The proper way to handle GDB PR Message-ID: <20050627124522.GA9819@nevyn.them.org> Mail-Followup-To: Wu Zhou , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00255.txt.bz2 On Mon, Jun 27, 2005 at 05:20:00PM +0800, Wu Zhou wrote: > Hello maintainers, > > I took up some fortran related PRs recently, but encountered some problem > while handling them. Anyone could help me out? TIA. > > 1. My replies to gdb-prs@sources.redhat.com are all returned back by one > of our internal mailer daemon. It said that gdb-prs is an unknown user in > sources.redhat.com domain. But I can rereive mails from the same users. > > When handling PRs, could I reply to gdb-prs directly? If not, how could > the correspondence between the owner and the submitter be recorded by PR > system? You have to reply to gdb-gnats, instead. No, I'm not precisely sure why. > 3. I see from the PR system that I can edit the PR, or add notes or send > email to interested parties. But IMHO all of them are not the most proper > way to handle user bug report. Why not consider using bugzilla (or others) > to replace it? Just my two cents anyway. We're going to. We haven't found time to make the switch. -- Daniel Jacobowitz CodeSourcery, LLC