Lots of pkgdb mail on commits list

[Ville Skyttä]

On Tuesday 21 August 2007, Toshio Kuratomi wrote:
> Ville Skyttä wrote:
> > Hello,
> >
> > Operations on the pkgdb appear to result in lots and lots of mail on the
> > commits list, one high level operation such as orphaning a package
> > appears to often spew around ten mails.
>
> If you're getting ten messages then there's something wrong.  Orphaning
> packages is currently generating one notification per branch[1]_....

Ok, that seems to be true, but my example was just a general one.  The 
orphaning case seems to be related to people for some reason tweaking EOLd 
branches.

> > This makes following the commits list much harder than before.  Is
> > reducing the number of these messages being worked on (eg. grouping
> > results of a single high level operation into one mail instead of sending
> > one for each bit)?  I can of course add local filters to take care of it,
> > but that's just a band aid.
>
> ...but I definitely agree that there is too much mail being sent even if
> it's only half that amount.

Yep, and for some things such as "add Joe Packager as a co-maintainer for foo" 
it's even worse than that, for example adding Dmitry as co-maintainer for 
mail-notification has resulted in 24 mails thus far.

elinks -dump 
https://www.redhat.com/archives/fedora-extras-commits/2007-August/thread.html | 
grep '\[pkgdb\].*mail-notification'

> Some options:
[...]
> Comments, other options?  I'm currently leaning towards implementing #2
> short term (by end of week) and working on #3 and #1 on a broader time
> frame.

1-3 sound fine to me, but I'd also like to suggest considering either 
directing the pkgdb messages to a completely separate list, or adding some 
topic categories in mailman config for the commits list.