I've been trying to hold my tongue on this, but I can't any longer. Is there something we can do about gigantic commits like this? This commit generated a 660KB email! Nobody is reading these emails. I'm already opposed to having automatically generated content committed to CVS, but when I'm receiving gigantic emails like this it's too much.
Hmmmmm, sorry. I'd see some alternatives - split the commit (e.g. by language) - create a new docs-cvs-mailinglist - drop the generated files and build the stuff online and for every release (RM job, resp. the tarball roller's) - would need some MBs of Java stuff installed everywhere - ?
Even if we don't drop the generated files in the repository (which I won't really comment on, other than that Java on FreeBSD isn't very stable - which matters because daedalus is on FreeBSD - someone may want to try to generate the docs on daedalus itself), I think the best overall solution would be to alter the CVS mailer script to send ViewCVS URLs to all of the files that changed when the entire diff exceeds a certain limit. Commits that exceed the mailing list threshold are dropped and that's not good *ever*.
I imagine some Perl hacker could tweak logaccum.pl to do this (/home/cvs/CVSROOT/log_accum.pl). If not, well, it might be time to rewrite logaccum.pl into Python. =) -- justin
