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 AF5CD138334 for ; Sat, 28 Dec 2019 09:27:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 32DCBE0BF0; Sat, 28 Dec 2019 09:27:15 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A894BE0BEC for ; Sat, 28 Dec 2019 09:27:14 +0000 (UTC) Received: from katipo2.lan (unknown [203.86.205.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kentnl) by smtp.gentoo.org (Postfix) with ESMTPSA id 7901B34DC3F for ; Sat, 28 Dec 2019 09:27:13 +0000 (UTC) Date: Sat, 28 Dec 2019 22:27:02 +1300 From: Kent Fredric To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Keywordreqs and slacking arch teams Message-ID: <20191228222702.017cbbaa@katipo2.lan> In-Reply-To: References: Organization: Gentoo X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/p93j0P8qX6KwwlxWKYcdzmi"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Archives-Salt: 14bb9d7d-4675-43eb-bc13-efe9dd5bb0ae X-Archives-Hash: d0aade60459bea64c7416bb599bc9f47 --Sig_/p93j0P8qX6KwwlxWKYcdzmi Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, 28 Dec 2019 08:09:33 +0100 Micha=C5=82 G=C3=B3rny wrote: > How can we improve this? Every time this kind of issue comes up, I can't help feeling we need some sort of tool more advanced than what we currently have. Something that maintains persistence of keyword demands similar to how the current bot does, but more ...=20 Its the sort of thing I get tempted to implement myself, but get too horrified about the prospect of working with portage internals to do it. --Sig_/p93j0P8qX6KwwlxWKYcdzmi Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEgdrME8Lrmai3DXYJda6SGagVg7UFAl4HH+YACgkQda6SGagV g7XIiBAAizK2TSuBNawwzuxFHSkf8zRLki5SliBefmlJQG9iP7gtAXDBuxkSlWF2 /5pmhdEgzp8/JfNwMA3xspyWLA/6Xbo6j2uklzK6lwiUihucfuHQRWJno9f/Aktp on5lNtRIGipuAMGYrLFmgeEZLiyC9bJu79btNQyQiuXfQFuqz9azE1iOszFygtMr VJsE8SscKqkdEVSgG5BzCo8SXcUeigiXQ1S+KEWVpB2+mNzOqeCwxP7aU/DrsW51 oKMq9do9kKi5GQqf17aGJ+5bPkyEX8dfjIV6iuezllMgvi9LkvH5c3+UOcbvwMde dN+6JxSYXk9BX8GhuqXwMnZiFpVI/SdeLKE48t6lMqJe6WYLJDqi8TSnmCH379kY nRaWvOgB8mnaj1VHCMveXpIPqOMb3/cx9m9mNIxy/rNM0NUgNb66+FQ3EwfVJHra jf4jR5T/QCifd78VOA5p1bl/Rw7dEi/0yuU+DwsdTeb5ySvJ0LxrKbn58mB0C67Q 8QxbyHmkjuKPdOSHZIooumSFW9i3mKm794vjsBMN9NIxwk/j1LSljGauKOLBoapC 6KEPJQPHd1PsScafryyWaggYKPn3IP3AfyVkSAd+XqFd2TF1+V4u4uLljdT80Nro TVD8KK/3WtJW+q14FyDMogcR2FDoyo3VDoIRc2w7Pa3ZAAOFxPg= =b95Q -----END PGP SIGNATURE----- --Sig_/p93j0P8qX6KwwlxWKYcdzmi--