This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Some bug policies [Was: Bug Digest 5/24]
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Wolfgang Bangerth <bangerth at ices dot utexas dot edu>
- Cc: Giovanni Bajo <giovannibajo at libero dot it>, Dara Hazeghi <dhazeghi at yahoo dot com>, gcc-bugs at gcc dot gnu dot org, Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>, Christian Ehrhardt <ehrhardt at mathematik dot uni-ulm dot de>, Andrew Pinski <pinskia at physics dot uc dot edu>
- Date: Tue, 27 May 2003 00:03:44 -0400 (EDT)
- Subject: Re: Some bug policies [Was: Bug Digest 5/24]
- References: <Pine.LNX.4.44.0305262249570.13914-100000@gandalf.ices.utexas.edu>
On Mon, 26 May 2003, Wolfgang Bangerth wrote:
>
> > > > Also, we could add a
> > > > keyword "patch-pending" for bugs whose patch was not reviewed yet (but I
> > > > kind of fear that reviewers are not going to query for it often...)
> > >
> > > Correct. Thus useless.
> >
> > Well, you can make it requestable, which would email the person in
> > question when you made the review request, and would appear in their
> > request queue (accessible as "My requests" from the footer).
>
> I think it's not so nice to make someone responsible for something without
> asking him before.
It doesn't make them responsible, it's simple a request.
:)
besides, if they are the maintainer, they already *are* actually
responsible, so
it's not really a problem anyway.
>
> Let's not make things too complicated. We don't have many patches in
> bugzilla,
THis, hopefully, should change for precisely the reason you've mentioned:
It's easy to have patches ignored on gcc-patches.
I would hope this is more because nobody decides it's their job to look at
it, than it is that new contributors are intentionally ignored.
If this is indeed the problem, then managing patches through bugzilla (or
*something*, i just mention bugzilla because it can be set up for doing
this) would hopefully help solve this.
It seems to work for other projects.
The only thing that makes it not a good idea yet is that i haven't
integrated the patch viewer yet.
> If things change over time, we can still ask for implementing something
> like what you suggest.
>
> Keep to Einstein's rule "Make it as simple as possible, but not simpler"
>
> W.