This is the mail archive of the gcc-patches@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] |
This is understandable. In any case, it would probably best to have a human in the loop before submitting patches to autobuilders, both for security reasons and as a sanity check, to avoid wasting resources on an unacceptable patch. Machine donors (maybe SuSE?) would authorize a small number of people to submit patches to the auto-builder after an initial review.
I guess I understood wrongly what the problem was. I believed that there was a shortage of human reviewers and that by "wasting resources" you meant someone reviewing a patch that doesn't even pass the testsuite, and thus, the pre-review batch test was a way to avoid wasting (human) resources on an unacceptable patch. Sorry for the confusion.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |