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 1ObaXl-0001JX-8h for garchives@archives.gentoo.org; Wed, 21 Jul 2010 14:45:09 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A2632E0B21; Wed, 21 Jul 2010 14:45:07 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 5C323E0B1F for ; Wed, 21 Jul 2010 14:44:58 +0000 (UTC) Received: from [192.168.3.7] (cpe-74-77-194-18.buffalo.res.rr.com [74.77.194.18]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPSA id D1E401B4119 for ; Wed, 21 Jul 2010 14:44:57 +0000 (UTC) Message-ID: <4C4707E0.2050601@gentoo.org> Date: Wed, 21 Jul 2010 10:44:48 -0400 From: "Anthony G. Basile" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100716 Shredder/3.0.5 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Two herds (and four extra?) References: <20100721133422.32e4b8ae@epia.jer-c2.orkz.net> <1279715786.20687.13.camel@localhost> <20100721145833.1a7d84ad@epia.jer-c2.orkz.net> In-Reply-To: <20100721145833.1a7d84ad@epia.jer-c2.orkz.net> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: b897e832-150f-49ed-b4bb-3f0750f261f7 X-Archives-Hash: 18dc0a61703d1eebcc77e18f73e521a5 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/21/2010 08:58 AM, Jeroen Roovers wrote: > On Wed, 21 Jul 2010 13:36:26 +0100 > "Tony \"Chainsaw\" Vroon" wrote: > >> This was originally done because we were bypassing a herd (lead) in >> getting our updates in. Toning it down is not a problem, would just >> blueness in the list address your concerns? > > Current b-w policy is to assign to the first mentioned , > then CC all other s and s[1], so if blueness has no > problem with that, then sure. > > > jer > > > [1] Or why would you mention them separately? I think we should still > encourage developers to join herds. I would prefer the bugs be assigned to hardened-kernel@gentoo.org and cc'ed to hardened@gentoo.org. All relevant devs should be on one or the other list. However, I am currently the principle maintainer of h-s. The reason for my preference is 1) that's how we have been doing it since before my time and that's how we keep track of bugs. See [1] for links to the open hardened-kernel bugs. 2) There is a close relationship between hardened-kernel and hardened. They are not two separate projects. The only reason for the two lists is to help keep the issues straight: kernel issues to hardened-kernel and userland/toolchain issues to hardened. [1] http://dev.gentoo.org/~blueness/hardened-sources/ - -- Anthony G. Basile, Ph.D. Gentoo Developer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxHB+AACgkQl5yvQNBFVTVK+wCgoA/CQPUwAwiOihjvkL2JfeZq Rh0AoIgEPP8MfrRUNyRSRLcwg2W/quyF =Qhls -----END PGP SIGNATURE-----