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