Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained?

[Amit Shah <amit.shah@redhat.com>]

On (Thu) Sep 10 2009 [08:56:34], Anthony Liguori wrote:
>>
>> 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.

How about a bot that goes through your mailbox (or your git queue) and
sends the email? One reply-to-all email for each unique hash you have
against qemu-master?

> 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).

... and store the commit ids and subject in some file. When you rebase
and that particular commit-id + subject combination is not present, an
auto-email can be triggered

> Usually, if I remove a patch from the queue because something is wrong  
> with it, I send out an email explaining what is wrong.

... but this is simpler and more efficient also because you can give the
reason along with the email rather than people mailing you later asking
why the patch was dropped.

		Amit