On Wed, Jul 15, 2015 at 4:22 PM, Mihai Moldovan wrote: > On 15.07.2015 04:13 PM, Mojca Miklavec wrote: >> Is there any sane way to allow "silent changes" in tickets where >> zillions of ports need to be changes (and lots of maintainers have to >> be subscribed)? > > No, hence:
I'm still optimistic that someone will point out some useful trac plugin to fix the "issue". > a comment that is periodically updated (which is quiet when being > edited.) > > Developers are required to reply to MP-dev to indicate they changed a port. > They > MUST NOT add a comment to the ticket (this would trigger more spam mails.) After some more thought: in what way is sending an email to every single subscriber of macports-dev (where people cannot even unsubscribe and where every maintainer is supposed to be subscribed) considered "less spam" than sending an email to every maintainer of an affected port (where people can actually unsubscribe easily)? > If they don't, I'll have to infer changes from the svn log/trac timeline, but > there's no guarantee I'll catch everything. This is about one particular ticket where you volunteered to do the work (but even then I would ask developers to mail just to you, not to the whole mailing list). But we have a "wider problem". I didn't ask this question just for the sake of a single ticket. > The developer who created the comment is the only one who may edit this > comment. > I think I saw ryan edit other comments (mine) before, but am not sure (and in > any case, this functionality might be reserved for portmgr and it should > probably stay that way. It's likely a global option we don't want to out > freely.) I still hope that some better solution must exist somewhere. Mojca _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
