This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Patch approval process suggestion
- From: Bruce Korb <bkorb at veritas dot com>
- To: GCC-patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 31 Mar 2003 09:54:09 -0800
- Subject: Patch approval process suggestion
- Reply-to: bkorb at veritas dot com
Use the web. :-) Stamp each gcc-patches email with an shtml address
that can be used to mark emails as "approved" and update a database.
It doesn't matter if it is a patch request or not. That database
can be consulted for emitting "no response" messages for patch
messages that have not been approved, denied or withdrawn.
I'd suggest the "patch message" criterion be the first line contains
"Approval request:" because often times patches show up in the middle
or end of a thread. That means ``Re: [patch] ...'' may be a patch.
It might not be, too. Keep the criteria simple.