1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 07/21/2010 08:58 AM, Jeroen Roovers wrote: |
5 |
> On Wed, 21 Jul 2010 13:36:26 +0100 |
6 |
> "Tony \"Chainsaw\" Vroon" <chainsaw@g.o> wrote: |
7 |
> |
8 |
>> This was originally done because we were bypassing a herd (lead) in |
9 |
>> getting our updates in. Toning it down is not a problem, would just |
10 |
>> blueness in the list address your concerns? |
11 |
> |
12 |
> Current b-w policy is to assign to the first mentioned <maintainer>, |
13 |
> then CC all other <maintainer>s and <herd>s[1], so if blueness has no |
14 |
> problem with that, then sure. |
15 |
> |
16 |
> |
17 |
> jer |
18 |
> |
19 |
> |
20 |
> [1] Or why would you mention them separately? I think we should still |
21 |
> encourage developers to join herds. |
22 |
|
23 |
I would prefer the bugs be assigned to hardened-kernel@g.o and |
24 |
cc'ed to hardened@g.o. All relevant devs should be on one or the |
25 |
other list. However, I am currently the principle maintainer of h-s. |
26 |
|
27 |
The reason for my preference is 1) that's how we have been doing it |
28 |
since before my time and that's how we keep track of bugs. See [1] for |
29 |
links to the open hardened-kernel bugs. 2) There is a close |
30 |
relationship between hardened-kernel and hardened. They are not two |
31 |
separate projects. The only reason for the two lists is to help keep |
32 |
the issues straight: kernel issues to hardened-kernel and |
33 |
userland/toolchain issues to hardened. |
34 |
|
35 |
|
36 |
[1] http://dev.gentoo.org/~blueness/hardened-sources/ |
37 |
|
38 |
|
39 |
- -- |
40 |
Anthony G. Basile, Ph.D. |
41 |
Gentoo Developer |
42 |
-----BEGIN PGP SIGNATURE----- |
43 |
Version: GnuPG v2.0.15 (GNU/Linux) |
44 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
45 |
|
46 |
iEYEARECAAYFAkxHB+AACgkQl5yvQNBFVTVK+wCgoA/CQPUwAwiOihjvkL2JfeZq |
47 |
Rh0AoIgEPP8MfrRUNyRSRLcwg2W/quyF |
48 |
=Qhls |
49 |
-----END PGP SIGNATURE----- |