From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16762 invoked by alias); 25 Nov 2004 18:03:18 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 16732 invoked from network); 25 Nov 2004 18:03:13 -0000 Received: from unknown (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org with SMTP; 25 Nov 2004 18:03:13 -0000 Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id iAPIACuR026593 for ; Thu, 25 Nov 2004 10:10:12 -0800 (PST) Received: from relay2.apple.com (relay2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.3.14) with ESMTP id ; Thu, 25 Nov 2004 10:03:13 -0800 Received: from apple.com (vpn1priv-33.apple.com [17.219.202.33]) by relay2.apple.com (8.12.11/8.12.11) with ESMTP id iAPI3AsA012440; Thu, 25 Nov 2004 10:03:11 -0800 (PST) Date: Thu, 25 Nov 2004 18:03:00 -0000 Subject: Re: Mainline in regression-fix mode after Thanksgiving Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v553) Cc: Giovanni Bajo , Janis Johnson , Mark Mitchell , gcc@gcc.gnu.org To: Richard Sandiford From: Mike Stump In-Reply-To: Message-Id: <43EC454A-3F0C-11D9-B4ED-003065BDF310@apple.com> Content-Transfer-Encoding: 7bit X-SW-Source: 2004-11/txt/msg00982.txt.bz2 On Thursday, November 25, 2004, at 02:44 AM, Richard Sandiford wrote: > For example, if I'm in a bug-fixing mood, the first thing I'll do is > search bugzilla for MIPS PRs. And since this is something I do in my > spare time, I don't want to waste it by duplicating other people's > work. > So I'll pick the bugs that aren't yet assigned to anyone. What has your experience been taking bugs from others to work and fix them? All I can say is that my running experience is that collisions happen less than once a decade. If you are worried about it, take the bug a week before you start working on it. I'm assuming that bugzilla emails the assigned on state change. If it became a problem, we can always have a state, actively working on this, or people could annotate the bug report that it is being worked on, or just send the person email asking if they are working on it. In the olden days, PRMS was used for bug activity and used emacs to edit bug reports, and the emacs locking mechanism was enough to alert to the fact someone was editing the bug report. If everyone changed but didn't save the report when they start on the bug, then one winds up with a nice light weight mechanism that solves the problem.