From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: Bernhard Kauer <kauer@os.inf.tu-dresden.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained?
Date: Thu, 10 Sep 2009 08:56:34 -0500 [thread overview]
Message-ID: <4AA90592.7080100@codemonkey.ws> (raw)
In-Reply-To: <20090910070336.GD3351@amit-x200.redhat.com>
Amit Shah wrote:
> On (Wed) Sep 09 2009 [08:00:28], Anthony Liguori wrote:
>
>> Bernhard Kauer wrote:
>>
>>> Its wednesday again, time to resend a patch to the list.
>>> Until today the following happened in this endless story:
>>>
>>>
>> Really, the whining just makes me want to drop your patch..
>>
>
> Let's be courteous and not drive away contributors.
>
> There's no relation between accepting patches and some nudging on the
> contributor's part especially when there's no feedback on patches;
> positive or negative.
>
> If there'd be a daemon sending a mail saying the patch is in some
> staging queue it'll reduce everyone's effort. Such extra mails
> definitely aren't a problem. If it's later reverted because of any kind
> of failure, again a polite mail wouldn't hurt.
>
The problem is patch volume. We often see hundreds of patches a day.
If typing a mail for each patch takes 2 minutes, that's potentially
hours spent just on sending these mails.
What I really need is some way to automatically generate these
notifications. It's pretty easy to send a mail when a patch enters the
queue but it's more difficult to send a mail when a patch is removed
from the queue via a rebase. Often times, I remove patches from the
queue simply because I'm not the right path for the patches to be
committed from (like linux-user).
Usually, if I remove a patch from the queue because something is wrong
with it, I send out an email explaining what is wrong.
Regards,
Anthony Liguori
> Amit
>
next prev parent reply other threads:[~2009-09-10 13:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 7:49 [Qemu-devel] [PATCH] [RESEND] RTC polling mode broken Bernhard Kauer
2009-09-09 12:18 ` [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Bernhard Kauer
2009-09-09 12:23 ` Amit Shah
2009-09-09 12:58 ` Bernhard Kauer
2009-09-09 12:25 ` Kevin Wolf
2009-09-09 13:00 ` Anthony Liguori
2009-09-09 13:26 ` Gleb Natapov
2009-09-09 13:45 ` Anthony Liguori
2009-09-09 14:31 ` Avi Kivity
2009-09-09 13:34 ` Bernhard Kauer
2009-09-10 7:03 ` Amit Shah
2009-09-10 7:56 ` Reimar Döffinger
2009-09-10 10:08 ` Amit Shah
2009-09-10 11:47 ` Luiz Capitulino
2009-09-10 12:01 ` [Qemu-devel] QEMU patch management Amit Shah
2009-09-10 12:29 ` [Qemu-devel] " Luiz Capitulino
2009-09-10 12:51 ` Reimar Döffinger
2009-09-10 13:11 ` Luiz Capitulino
2009-09-10 17:24 ` Reimar Döffinger
2009-09-10 13:58 ` [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Anthony Liguori
2009-09-10 13:56 ` Anthony Liguori [this message]
2009-09-10 14:04 ` Amit Shah
2009-09-10 14:12 ` Anthony Liguori
2009-09-10 15:15 ` Amit Shah
2009-09-10 14:38 ` Avi Kivity
2009-09-10 15:54 ` Anthony Liguori
2009-09-10 16:09 ` Avi Kivity
2009-09-10 16:22 ` Anthony Liguori
2009-09-10 16:35 ` Avi Kivity
2009-09-10 16:38 ` Anthony Liguori
2009-09-10 16:46 ` Avi Kivity
2009-09-10 17:19 ` Reimar Döffinger
2009-09-11 12:39 ` Amit Shah
2009-09-12 5:55 ` Blue Swirl
2009-09-13 15:44 ` Avi Kivity
2009-09-13 16:30 ` Blue Swirl
2009-09-11 7:06 ` Gerd Hoffmann
2009-09-10 18:29 ` Mark McLoughlin
2009-09-10 18:40 ` Avi Kivity
2009-09-10 19:31 ` Anthony Liguori
2009-09-13 15:49 ` Avi Kivity
2009-09-10 20:36 ` Mark McLoughlin
2009-09-13 16:19 ` Avi Kivity
2009-09-14 7:49 ` Mark McLoughlin
2009-09-14 7:59 ` Avi Kivity
2009-09-10 18:59 ` Reimar Döffinger
2009-09-10 16:05 ` Anthony Liguori
2009-09-10 16:14 ` Avi Kivity
2009-09-11 9:16 ` [Qemu-devel] commit e09a5267 (was: [PATCH] [RESEND2] Qemu unmaintained?) Jan Kiszka
2009-09-11 12:56 ` [Qemu-devel] Re: commit e09a5267 Anthony Liguori
2009-09-11 13:04 ` Jan Kiszka
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=4AA90592.7080100@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=amit.shah@redhat.com \
--cc=kauer@os.inf.tu-dresden.de \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).