From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NvZEk-0004L2-4q for garchives@archives.gentoo.org; Sat, 27 Mar 2010 16:51:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C070BE0838; Sat, 27 Mar 2010 16:51:47 +0000 (UTC) Received: from qw-out-1920.google.com (qw-out-1920.google.com [74.125.92.148]) by pigeon.gentoo.org (Postfix) with ESMTP id B3D36E085D for ; Sat, 27 Mar 2010 16:51:41 +0000 (UTC) Received: by qw-out-1920.google.com with SMTP id 5so1273468qwf.10 for ; Sat, 27 Mar 2010 09:51:41 -0700 (PDT) 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 Sender: antarus@scriptkitty.com Received: by 10.229.46.11 with HTTP; Sat, 27 Mar 2010 09:51:41 -0700 (PDT) In-Reply-To: <20100327171641.TAdd9e4.tv@veller.net> References: <4B9A936B.3070804@gentoo.org> <4BAE15A6.80101@gentoo.org> <20100327171641.TAdd9e4.tv@veller.net> Date: Sat, 27 Mar 2010 16:51:41 +0000 X-Google-Sender-Auth: fd68537f55c8bc05 Received: by 10.229.217.14 with SMTP id hk14mr1387496qcb.89.1269708701227; Sat, 27 Mar 2010 09:51:41 -0700 (PDT) Message-ID: Subject: Re: [gentoo-dev] Re: Handling of keywording bugs with only one arch From: Alec Warner To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: f0e339b0-d408-4543-81f9-f3aa1ef511d6 X-Archives-Hash: 833a0cb9247b7a1a691ab4a90684068c On Sat, Mar 27, 2010 at 4:45 PM, Torsten Veller wrote: > * Petteri R=C3=A4ty : >> So let's summarize for assigning to the single arch: > >> In support (and my comments in support): >> =C2=A0- Can be used as a gentle reminder for slacker arches > > And if not "only one arch" or "single arch" is slacking? > I guess you would find another gentle way to remind them. > > > How about a tool generating mails to arch teams, which lists all > STABLEREQ, KEQWORDREQ bugs to which the arch team is CC'ed for a month? > (Or probably easier or possible at all: which weren't changed for 30 days= .) I'd opt for a webpage personally. I have found that push-nag systems work well at first until the nagging increases to a level where the nag-ee just filters the mail away. This happens often at work. For example I get emails telling me to delete unused perforce clients; but those mails just get marked as read by a filter and archived. Could we generate a bugzilla search for arch teams? Do arch teams already use existing bugzilla functionality? -A > >