Re: Sending diffs of `elpa' to the respective maintainers

[Glenn Morris <rgm@gnu.org>]

Stefan Monnier wrote:

>> Maybe someone on this list will feel inspired to write this piece...
>
> Hopefully.

Apparently not.

I implemented:

1) --create; to scan the packages directory and write all recognizable
   maintainers to a file. Eg in the admin/ directory, try:

./forward-diffs.py --create -p ../packages -m maint.txt

No need to keep maint.txt in version control.

2) If a changed file has an unknown maintainer, it will scan the file
for the maintainer and if found add it to the maintainer file.
(So the maintainer file isn't really needed, but it makes things a
little faster.)


3) opt-out through an override file, overmaint.txt, where you can use
"nomail" for maintainer.


"Someone" needs to actually put it into use.

I suggest running --create once an hour or somesuch from cron, and the
normal mode of operation from procmail as previously suggested.

"Someone" also needs to ensure all packages have recognizable maintainer
emails. (DOT AT obfuscation is handled.) Several do not (eg company).