This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] autopinger
Ben Elliston wrote:
>> I'm shortly sending a first test of my autopinger script for pending
>> patches to gcc-patches@. Any comments are welcome. The plan would be
>> running it weekly.
>
> What does it do, exactly?
It goes through Bugzilla looking for bugs with the keyword "patch" set, and
with a comment containing a link to the gcc-patches (or java-patches) mailing
list. Bugs matching this criteria are considered with a patch pending for
review. It generates a mail with an attacchment containing information on such
bugs, ordered by component, including PR number, PR title, Patch author, date
of patch, link to gcc-patches, link to PR in Bugzilla.
To "register" a posted patch to the automatic pinger, go to the corresponding
Bugzilla entry (if any -- or you can open one), add the keyword "patch", and a
comment with a link to the patch. Notice that this is a standard convention
already in practice among maintainers and Bugmasters for a long time already.
Patchpinger just relies on this because it is already being done.
To "deregister" a patch which was rejected by the review, just remove the
keyword "patch" from the bug.
The automatic pinger was designed to *not* force maintainers to learn/use a new
way of handling patches. It relies on widely used conventions, and does not
force people to do special things they never did before. In other words, it is
mostly *transparent* to users.
Giovanni Bajo