Re: Maybe it's time to split debian-devel-changes

[Jim Pick <jim@jimpick.com>]

I already filter these with some mailing filtering rules.

My mailagent .rules looks like this:

<LIST> X-Loop: /debian-devel-changes@lists.debian.org/i { REJECT CHANGES };
<CHANGES> Subject: /\(.*source.*\)/ { SAVE Debian.debian-devel-changes.source };
<CHANGES> Subject: /\(.*hurd-i386.*\)/ { SAVE Debian.debian-devel-changes.hurd-i
386 };
<CHANGES> Subject: /\(.*i386.*\)/ { SAVE Debian.debian-devel-changes.i386 };
<CHANGES> Subject: /\(.*alpha.*\)/ { SAVE Debian.debian-devel-changes.alpha };
<CHANGES> Subject: /\(.*powerpc.*\)/ { SAVE Debian.debian-devel-changes.powerpc 
};
<CHANGES> Subject: /\(.*arm.*\)/ { SAVE Debian.debian-devel-changes.arm };
<CHANGES> Subject: /\(.*sparc.*\)/ { SAVE Debian.debian-devel-changes.sparc };
<CHANGES> Subject: /\(.*m68k.*\)/ { SAVE Debian.debian-devel-changes.m68k };
<CHANGES> All: /./  { SAVE Debian.debian-devel-changes };

Crude, but it works nicely.

It still might be a good idea to split the lists however.

Cheers,

 - Jim