From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45148) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbFRG-0000uL-Vk for qemu-devel@nongnu.org; Thu, 26 Mar 2015 17:35:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YbFRD-0002TA-QW for qemu-devel@nongnu.org; Thu, 26 Mar 2015 17:35:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55652) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbFRD-0002T3-Go for qemu-devel@nongnu.org; Thu, 26 Mar 2015 17:35:39 -0400 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id 78731B6E6F for ; Thu, 26 Mar 2015 21:35:38 +0000 (UTC) Message-ID: <55147BA9.3070309@redhat.com> Date: Thu, 26 Mar 2015 17:35:37 -0400 From: John Snow MIME-Version: 1.0 References: <87h9t9i15j.fsf@blackfin.pond.sub.org> <5512D81D.5000309@redhat.com> <20150326131905.GB3932@noname.redhat.com> In-Reply-To: <20150326131905.GB3932@noname.redhat.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Bouncing maintainers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: Markus Armbruster , qemu-devel@nongnu.org On 03/26/2015 09:19 AM, Kevin Wolf wrote: > Am 25.03.2015 um 16:45 hat John Snow geschrieben: >> >> >> On 03/25/2015 10:48 AM, Markus Armbruster wrote: >>> I just had another cc: to an address gotten from MAINTAINERS bounce with >>> "user unknown". >>> >>> How do we weed out dead MAINTAINERS entries? >>> >> >> Automated spambot that runs once a release cycle and reports back to >> the list which entries were dead? > > I don't need more email. Why can't we just send a patch to MAINTAINERS > dropping the line the first time someone actually notices it? > > Kevin > Could make a bot that just watches from: addresses on the list. If it sees a mail from you within the last release cycle, it assumes you are still alive. If it doesn't hear from you for an entire release cycle, it sends out a small ping and looks for bounces. Only once a release would be not more than four times a year, and most active maintainers would never see a single email. Or, yes, manually when it happens...