From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, Yao Qi <yao@codesourcery.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] gdb/CONTRIBUTE update
Date: Fri, 01 Mar 2013 16:51:00 -0000 [thread overview]
Message-ID: <87a9qnukrs.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20130301164043.GA10424@host2.jankratochvil.net> (Jan Kratochvil's message of "Fri, 1 Mar 2013 17:40:43 +0100")
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
prev parent reply other threads:[~2013-03-01 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 20:26 Jan Kratochvil
2013-02-21 21:01 ` Tom Tromey
2013-02-26 9:32 ` Yao Qi
2013-02-26 9:38 ` Jan Kratochvil
2013-02-26 9:52 ` Yao Qi
2013-02-26 13:16 ` Jan Kratochvil
2013-02-26 11:16 ` Pedro Alves
2013-02-26 13:12 ` Jan Kratochvil
2013-02-28 20:01 ` Tom Tromey
[not found] ` <20130228212725.GA1848@host2.jankratochvil.net>
2013-03-01 16:27 ` Tom Tromey
2013-03-01 16:41 ` Jan Kratochvil
2013-03-01 16:51 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9qnukrs.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=yao@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox