From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlkGZ-0004pk-SD for qemu-devel@nongnu.org; Thu, 10 Sep 2009 10:04:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlkGT-0004mO-60 for qemu-devel@nongnu.org; Thu, 10 Sep 2009 10:04:51 -0400 Received: from [199.232.76.173] (port=50963 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlkGS-0004mD-Tc for qemu-devel@nongnu.org; Thu, 10 Sep 2009 10:04:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40338) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlkGS-0006ht-9k for qemu-devel@nongnu.org; Thu, 10 Sep 2009 10:04:44 -0400 Date: Thu, 10 Sep 2009 19:34:13 +0530 From: Amit Shah Subject: Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Message-ID: <20090910140413.GA28534@amit-x200.redhat.com> References: <20090902074905.GB25711@chrom.inf.tu-dresden.de> <20090909121817.GA21997@chrom.inf.tu-dresden.de> <4AA7A6EC.10907@codemonkey.ws> <20090910070336.GD3351@amit-x200.redhat.com> <4AA90592.7080100@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AA90592.7080100@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Bernhard Kauer , qemu-devel@nongnu.org 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