- Fork before sending mail so that the commiter doesn't have to wait

- Support send mail on CVS 'import'

- Try to reproduce eclipe issue,
  http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&threadm=mailman.7436.1054886644.21513.bug-cvs%40gnu.org&rnum=6&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DISO-8859-1%26safe%3Doff%26q%3Dcvsspam%26sa%3DN%26tab%3Dwg
  http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/cvs_features2.0/cvs-faq.html#server_8
  Add see if the problem could be helped by locking

- If a previously dead file is re-added, it is noted as a modification, rather
  than an add.  Introduce 're-add' change-type if possible?

- Use CSS :after{content:"M^"} for add/rem DOS-end-of-line, rather than having
  "^M" in the body text.

- Work out alternatives to id attribute used by CSS, 'cos of complaints...
  http://validator.w3.org/check?uri=http%3A%2F%2Fwww.badgers-in-foil.co.uk%2Fprojects%2Fcvsspam%2Fexample.html&charset=iso-8859-1+%28Western+Europe%29&doctype=XHTML+1.0+Transitional

- what happens when the only change to a file is an edit to an RCS keyword,
  and we are suppressing such changes?

- what happens when someone is using module names?

- test if removing a 'very long' file clashes with 'supress deleted diff' opt
  (will it still give "X lines skipped" msg?)

- KMail (debian woody) doesn't highlight TODO in diffs

- If a 'module' option is specified, include this text in tmpfile names to
  stop multi-repository commits colliding where they are actually configured
  seperately.  Special chars in 'module' will need encoding (underscores?).

- Customizable "show functions" option (a-la CVSweb)
  teach rcsdiff(1) to recognize function lines for each filename-regex
  (useful?)


For version 0.3.x

- config file is a bit kludgy.  optionNamesShould at_least_be_consistent
  should not be ruby code

- abstract XML (xhtml) generation into an external file

- Some way of using taginfo too (send mail from cron?)

- Monitor for additions of directories (again mail from cron?)

- Genertate text/plain messages too (have --plain-to and --html-to opts)

- Add comment to Bugzilla entry when log mentions a bug (in addition to the
  link to the bug).  Send mail to Bugzilla's contrib/bugzilla_email_append.pl
  or use libdbd-mysql-ruby?