| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
I tend to agree with tommy. |
| 5 |
It's also difficult to reflect your attitude regarding your ebuilds |
| 6 |
being touched, cause it may differ depending on the subject of the |
| 7 |
change and who makes the change. So in the end it may boil down to a |
| 8 |
conversation anyway. |
| 9 |
|
| 10 |
For things like your subslot example I am wondering if it could be |
| 11 |
possible to do a dev-announce that packages will be touched by a group |
| 12 |
of devs, cause of important migration and that maintainers who don't |
| 13 |
feel comfortable with that can require a bug/patch. |
| 14 |
|
| 15 |
While waiting for answers a few weeks you have the time to test that |
| 16 |
stuff in an overlay instead of reporting tons of bugs. |
| 17 |
-----BEGIN PGP SIGNATURE----- |
| 18 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 19 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 20 |
|
| 21 |
iQEcBAEBAgAGBQJQr5HrAAoJEFpvPKfnPDWzfCkIALNXbjH3xB6Mf837sVe8QM6q |
| 22 |
xGuCJlivRlJLfbANHa058En2tVRV1qee373RXDmnsM6PBeU7rc8XLGxd0lM2lswD |
| 23 |
48FCGo/8+AqBujLhY74FgXja/47b9WpcP3ZOw82/6bS8p4tcA5i665HHVbrLJ5VK |
| 24 |
Wwri8BBlExj5y0HFrHS0KKMDAHLzbNEMDGArINa1w6iwx/3hVHkgaZVgxY3UZohH |
| 25 |
D8A1BeTCoV5ZS3d890+BoVAYwCVKB6WiYfIdmpgmudweLgAmbqNkOnq8lQI88QmY |
| 26 |
EWoLyibKSg7jzQ7e22IwNP/QFByvXf5SxfomsB6VRSJJyrYGLMI7W1GWHI2z1+Q= |
| 27 |
=KoFo |
| 28 |
-----END PGP SIGNATURE----- |
Archives