From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0150113832E for ; Sat, 6 Aug 2016 16:14:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8DC5621C0AB; Sat, 6 Aug 2016 16:14:33 +0000 (UTC) Received: from foo.stuge.se (foo.stuge.se [212.116.89.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4A3D921C03A for ; Sat, 6 Aug 2016 16:14:31 +0000 (UTC) Received: (qmail 13802 invoked by uid 1000); 6 Aug 2016 16:01:46 -0000 Date: Sat, 6 Aug 2016 16:01:46 +0000 From: Peter Stuge To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Packages up for grabs Message-ID: <20160806160146.GE12988@foo.stuge.se> References: <1470471113.17315.5.camel@gentoo.org> <20160806133719.GD12988@foo.stuge.se> <20160806170954.4c2c544838f372217faba4ff@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160806170954.4c2c544838f372217faba4ff@gentoo.org> X-Archives-Salt: 107958c1-207d-4928-9751-8a6f9be34a13 X-Archives-Hash: 7d635216fbb2f2a18d9259667507f1de Andrew Savchenko wrote: > On Sat, 6 Aug 2016 13:37:19 +0000 Peter Stuge wrote: > > Hi Pacho, many thanks for your work, but.. .. > > ..do you think you can arrange to post everything in one mail, > > instead of 14 different ones in a single day? > > I suppose these posts are automated (at least partially), since > each of them is linked to a different retirement bug. That would explain the many emails - then it will probably be halfway straightforward to also bundle the bugs and send one email at say 2:00 am or whenever is a likely time that Pacho is not doing retiring. :) > So you shouldn't blame Pacho for his work. I don't think I was - I wanted to nudge to improve the output of his work. I like to follow what gets retired, in case I want to pick something up, but I don't like to read 14 emails in one day with a few packages in each. Another, maybe simpler, approach would be to have a stateless cronjob instead of a queue, the job would just look at what retirement bugs were changed (opened?) in the last while (day?), and send one email listing all packages. Maybe it could also set some status in the bug, to avoid duplicates because of DST or whatever. Thanks a lot //Peter