This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Maintainer policy for GDB
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Ian Lance Taylor <ian at airs dot com>
- Cc: msnyder at redhat dot com, gdb at sources dot redhat dot com
- Date: Sun, 27 Nov 2005 21:18:19 +0200
- Subject: Re: Maintainer policy for GDB
- References: <43893653.4080209@redhat.com> <m3ek52d6tf.fsf@gossamer.airs.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Cc: gdb@sources.redhat.com
> From: Ian Lance Taylor <ian@airs.com>
> Date: 26 Nov 2005 20:59:40 -0800
>
> For comparison, a gcc patch which causes a testsuite or significant
> performance regression on a primary target may be reverted, if any two
> people with write privileges (i.e., not just maintainers, but also
> write-after-approval) agree, after waiting for 48 hours. In practice
> this is rarely actually done; the threat of it is normally enough to
> resolve the situation one way or another.
Thanks for the info.
However, our problem was what to do when a patch does not cause
failures in the testsuite, but still causes objections.