1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 06/23/2013 05:01 AM, Rick "Zero_Chaos" Farina wrote: |
5 |
> On 06/22/2013 06:11 AM, Pacho Ramos wrote: |
6 |
>> El sáb, 22-06-2013 a las 00:06 +0000, Robin H. Johnson escribió: |
7 |
>> [...] |
8 |
>>> I'm not going into review systems here at all, I'm simply |
9 |
>>> trying to have a policy of what changes are welcomed/blocked |
10 |
>>> WITHOUT interaction from the listed maintainer(s) of a given |
11 |
>>> package/herd. |
12 |
>> [...] |
13 |
> |
14 |
>> In my case I would like to be always notified a change has been |
15 |
>> committed (even forwarding gentoo-commits message to me), that |
16 |
>> will help me to keep track of the committed changes, and learn |
17 |
>> more if they corrected a bug caused by me ;) |
18 |
> |
19 |
> I have myself on the gentoo-commits ML and then I filter out so |
20 |
> that just changes to my packages make it to me. You could further |
21 |
> filter so that just changes to your packages where you are not the |
22 |
> commiter make it to you... There is ample information in the |
23 |
> headers of the ML to do this kind of thing. |
24 |
> |
25 |
|
26 |
There is no meta information on the maintainer of a package (just the |
27 |
comitter). You'd have to create a filter rule for every single package |
28 |
afais, unless I'm missing something. |
29 |
-----BEGIN PGP SIGNATURE----- |
30 |
Version: GnuPG v2.0.20 (GNU/Linux) |
31 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
32 |
|
33 |
iQEcBAEBAgAGBQJRzIHnAAoJEFpvPKfnPDWz1mwIAK0Ku2fT0Nv0EdvERXv/AIsw |
34 |
EKnzSCCH01XKEVoP14ujXwD+JZQBKVkqOLICZN0hSUlkmYoUCJAxUtMrMp8dkoOX |
35 |
+yR4yfa5Gm62CbgxI836T0j644ii0Z6vTdvg7ZLKVWc1/sGF736dm63CsoBRFCaO |
36 |
Nk163csHShCYFdCUmdLZZGjGn2XYSbyA6hoS5Bjx8NrdaKHM6JDqB5UlcUlNjgQW |
37 |
cv/OVFWiWeLZZMZzkLeItuZQFEhfLrNpJdZuzoVDiuZZLW1AtIwbWTSW7z1L1HhN |
38 |
m2dtadw6xT9EoGnUM12gYKvPmiYiiulK/DCH5uJsyWGfA3ejmskGbR1a7ZCXSJM= |
39 |
=b87U |
40 |
-----END PGP SIGNATURE----- |