I've poked around the mailman interface and I can't say I've found an option to do any of these. We could try to change things so the committer's email is used rather than the patch authors.
ali On 03.02.2014 09:27, Andreas Sandberg wrote: > Would it be possible to whitelist certain mail servers instead? In that > case, we could just whitelist daystrom. > > Another option would be to use mailman's moderation support. It should > be possible to setup a moderation password in mailman and add a > 'x-approved: password' to emails generated by mercurial. I think this > works even if moderation isn't normally enforced, but it's hard to tell > since the mailman documentation is a bit sketchy at best. > > //Andreas > > On 2014-02-03 15:31, Steve Reinhardt wrote: > Yea, you are correct about the list restriction. We definitely want to keep > the restrictions on list posting to keep the spam down. That does have > unfortunate interactions with the changeset notifications though. What we've > done in the past is add email addresses to the list of "non-member addresses > whose postings should be automatically accepted" in mailman (mostly things > like work emails for people who are on gem5-dev with their personal emails, > and vice versa, along with some wildcards like *. umich.edu and *.arm.com). > It's kludgy but I don't know of another solution. If we could coerce the > commit messages to all come from some common email we could add that to the > list--or even just the person doing the push, as opposed to the person who > committed the patch--but I don't know how easy that would be. Steve On Mon, > Feb 3, 2014 at 2:07 AM, Andreas Sandberg <[email protected]>wrote: I > recently pushed a bug fix that a colleague authored and noticed that the > changeset not ifcation didn't make it to the list. Do we have list rules that prevent non-members from posting to the list? If so, are changeset notications posted as the committer or the author of a changeset? It's probably a good assumption that all committers are on the gem5-dev list, but I don't think it is going to be the case for all patch authors. //Andreas _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev [1] _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev [1] _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev [1] Links: ------ [1] http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
