From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1H6zAP-0007lv-Qv for garchives@archives.gentoo.org; Wed, 17 Jan 2007 01:00:42 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0H0xcP4006257; Wed, 17 Jan 2007 00:59:38 GMT Received: from slimak.dkm.cz (smtp.dkm.cz [62.24.64.34]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0H0xbgX027838 for ; Wed, 17 Jan 2007 00:59:37 GMT Received: (qmail 41926 invoked by uid 0); 17 Jan 2007 00:59:37 -0000 Received: from r141.net.upc.cz (HELO ?192.168.1.1?) (62.24.83.141) by smtp.dkm.cz with SMTP; 17 Jan 2007 00:59:37 -0000 Message-ID: <45AD74FA.5060307@gentoo.org> Date: Wed, 17 Jan 2007 01:59:38 +0100 From: Vlastimil Babka User-Agent: Thunderbird 2.0b1 (X11/20061210) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-java@gentoo.org MIME-Version: 1.0 To: gentoo-java@lists.gentoo.org Subject: Re: [gentoo-java] Weka package cleanup References: <93e475bc0701161132s19786436p8b241e22a163ec68@mail.gmail.com> <45AD2FBB.5040001@gentoo.org> <9e0cf0bf0701161234u48924125t1067de35252c6371@mail.gmail.com> <45AD3AE8.6020402@gentoo.org> <9e0cf0bf0701161255s695622abi19922367aa57799f@mail.gmail.com> <93e475bc0701161453y2488c4al4dae0e787a703b27@mail.gmail.com> <1168990676.13072.8.camel@wlt.obsidian-studios.com> <93e475bc0701161607s5ca219fcx1a03cca7f6acbfc3@mail.gmail.com> In-Reply-To: <93e475bc0701161607s5ca219fcx1a03cca7f6acbfc3@mail.gmail.com> X-Enigmail-Version: 0.94.1.0 OpenPGP: id=4E61DE84; url=subkeys.pgp.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: cd30d65c-38c2-4a43-af4b-8ffa8bb68202 X-Archives-Hash: 73f65ed8ad7c7dfba59c1680a6524a29 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alistair Bush wrote: > I have also though of going thru bugs.gentoo.org > and reassigning the priority of bugs into > categories (rather a large job for anyone who has other projects they > want to get kicking). And I would love to mark stable/keyword requests in a way that I can filter them easily. They are assigned to us but we are not the ones solving them :) Be it a special component or keyword, or some unified form of summary. I see there are already STABLE and TESTED keywords for arch testers to mark stuff they've tested, so maybe add something STABLEREQ and KEYWORDREQ? What do you think? If it's sane, it should probably be discussed on gentoo-dev as some global policy. - -- Vlastimil Babka (Caster) Gentoo/Java -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFrXT5tbrAj05h3oQRAtj7AJ9ydkaYZBKom7qZ0R6/lTlpSqbnHgCfWvKl hs3etexbXWaWM8N6WTtOHQQ= =ndHV -----END PGP SIGNATURE----- -- gentoo-java@gentoo.org mailing list