This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Mainline in regression-fix mode after Thanksgiving
- From: Mike Stump <mrs at apple dot com>
- To: Richard Sandiford <rsandifo at redhat dot com>
- Cc: Giovanni Bajo <rasky at develer dot com>, Janis Johnson <janis187 at us dot ibm dot com>, Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 25 Nov 2004 10:03:09 -0800
- Subject: Re: Mainline in regression-fix mode after Thanksgiving
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.