This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Patch approval process suggestion


Alexandre Oliva wrote:
> I'd much rather keep current state of affairs, and track patches
> awaiting approval by looking for `Ok to install?' or just `Ok?' in
> their bodies.  This would automatically rule out patches posted (and
> installed) by maintainers with global write privileges, and follow-up
> patches to messages that approved patches conditioned to minor
> changes.

I don't deal with this stuff on a daily basis, so it's more your call.
I was just imagining really elaborate schemes that would wind up
buggy or unimplemented.  I suggested a key phrase at the start 'cuz
then this message wouldn't trigger an approval check, even if it were
containing a sample patch.  :-)  (It contains "Ok?" and "Ok to install?",
*plus* 'Patch' in the subject. ;)  Main suggestion:  keep requests simple
and unambiguous, and reduce responses to a mouse click and a simple form.
A "good thing" for those of who are time constrained (or lazy).

Cheers - Bruce


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]