El jue, 13-09-2012 a las 03:43 +0200, Jeroen Roovers escribió: > On Wed, 12 Sep 2012 20:53:20 +0200 > Pacho Ramos <[email protected]> wrote: > > > > You can un-CC yourself. I don't see why security@ should be doing > > > the legwork. > > > > It shouldn't be so hard to do, they can do it just when they CC > > arches, instead of relaying some random team member to do it himself > > once a useless message is received > > It does become a chore when you have to check a list to match various > CC'd people's preferences and decide whether to un-CC them based on > that, the way they were CC'd (did they do it themselves, were they CC'd > by security, and so on) and perhaps some other factors someone will no > doubt soon propose in this thread. > > Basically you are saying, "why doesn't anyone else do my volunteer work > for me". > > > jer > >
I am not saying that, you can see who CCed them in history and most of times was security team who CCed them... anyway, per my just replied mail to Sean, I think we could reach a good compromise. What I don't understand is why you think I am trying to say that thing when I ever wasn't sure if maintainers were allowed to unCC themselves when they think
signature.asc
Description: This is a digitally signed message part
