This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] gdb/CONTRIBUTE update
- From: Tom Tromey <tromey at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Pedro Alves <palves at redhat dot com>, Yao Qi <yao at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Fri, 01 Mar 2013 09:50:31 -0700
- Subject: Re: [patch] gdb/CONTRIBUTE update
- References: <20130221202629.GA30015@host2.jankratochvil.net> <512C80DA.5070600@codesourcery.com> <20130226093829.GA5802@host2.jankratochvil.net> <512C9996.6000007@redhat.com> <20130226131213.GA15184@host2.jankratochvil.net> <87k3psw6x0.fsf@fleche.redhat.com> <20130228212725.GA1848@host2.jankratochvil.net> <87k3prulus.fsf@fleche.redhat.com> <20130301164043.GA10424@host2.jankratochvil.net>
Jan> That is the whole problem - how to keep the list of pending patches.
Jan> I maintain a list of my own patches I submitted. Another problem is that
Jan> older patches sometimes even reviewed no longer get a response by their
Jan> submitter so there should be also some response timeouts.
I think bugzilla would be better.
* User files patch in bugzilla, makes sure to tag the attachment as a patch
* Reviews can be done in bugzilla (or email? I forget if that is
enabled on sourceware, but if not perhaps we could set it up)
* A reviewer would put the bug into WAITING; we can randomly do queries
for this and close all WAITING bugs older than a year or two
* We could have a job anywhere to query bugzilla and send out weekly
ping reminders
To be clear, I don't object to your CONTRIBUTE change.
I have a suspicion that adding more work for the contributors is going
to mean more patches being dropped (by them), but time will tell.
Tom