____  _     _      _    
  / ___|| |__ (_) ___| | __ _
  \___ \| '_ \| |/ _ \ |/ _` |
   ___) | | | | |  __/ | (_| |
  |____/|_| |_|_|\___|_|\__,_|

  Shiela - Access Control and Logging Facility for CVS
  ____________________________________________________________________

  TODO

  For version 1.0:
  ----------------

  o  We could replace "cvs update -p -rX file" with "cvs diff -N -u3
     -Dyesterday file" to allow people to pass the log email directly to patch(1)
     and this way let new files beeing added. Same for deleted files.

  o  Subject can be compressed by reducing common prefix and 
     just repeating the subdirs together with the files:
     << [CVS] OSSP: ossp-pkg/ossp-cvs README.OSSP ossp-pkg/ossp-cvs/src cvsrc.c
     >> [CVS] OSSP: ossp-pkg/ossp-cvs README.OSSP src/cvsrc.c
     Eventuell sogar auf module reduzieren:
     >> [CVS] OSSP ossp-cvs: README.OSSP src/cvsrc.c

  o  Branches should be listed in Subject lines

  o  Modules should be allowed to be arbitrary paths and not
     just top-level directories. This should be easy to add for
     version 1.1 by adjusting the access control routine.

  o  Shiela perhaps should read in shiela.msg in order to know
     what to kick out when compressing the message. 

  For version 1.1:
  ----------------

  o  Under MIME mails, the details could include complete files
     really as is without the need to uuencode them first.

  o  Perhaps replace do_file() mit an IO::File based class?
     But keep always in mind \n characters when coming in and going out.

  o  Support for code freeze time (ranges) and automatic pre-time
     messages and MOTDs for reminder under cvs commit, cvs admin and cvs
     import actions.
     Idea: Req "Approved by:" *:core;

  o  Support for "Review-Than-Commit" style development.
     Idea: Req "Reviewed by:" *:devel;

  o  Be more relaxed and support case insensitive config file
     parsing to be less restrictive to the user when it comes
     to keywords.

  o  Support per-directory .shielarc[,v] files in the
     repository which act similar to the CVS watch facility and can forward
     the logging messages to particular people in addition to the standard
     logging as configured by shiela.cfg. So a .shielarc file with "Log
     mod_foo.c mail:rse@engelschall.com" would send an extra email to
     rse@engelschall when mod_foo.c was modified.  So, actually a "Log"
     command in .shielarc should act identically to a "Log" command in
     shiela.cfg.