Sometimes other devs want to change anything in ebuilds not maintained by them, most of times that changes are fine but other not. I think would be interesting if "repoman commit" could also mail to maintainer notifying him about committed change to let him see it faster and revert (if needed) or even let him know the fixed problem and how to prevent that fixed bug in future commits. I know the goal looks hard to implement but, anyway, I think would be interesting to try to do it if possible. Thanks Reproducible: Always
Why don't you just filter the gentoo-commits ML?
Because I would really have a lot of mails to fetch and review every day :/
(In reply to comment #0) > I think would be interesting > if "repoman commit" could also mail to maintainer Sending mails requires user-side mail configuration, for authentication with the a mail server. It seems error-prone and would probably be best implemented on the infrastructure side (if filtering the gentoo-commits ML is not feasible).
Yes, the idea would be more like sending mails "from infra side" when files are committed than every dev needing to configure mail 1. Files are committed 2. A mail is sent to maintainer when he is not the committer (and probably would be also interesting to not send mails when changes are only affecting to KEYWORDS, like stabilizations and so)
you can do that perfectly fine these days with filters on the commit messages list
maybe we should have the script generating commits include maintainer info extracted from the metadata.xml as X- tags, then people can filter based on the herds/users they care about.
repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.
I'll reopen for pkgcheck but not sure if we want to do this or not.
