From: Jim Kingdon
Date: 7 Mar 1998

The idea is to supplement (and eventually replace, but only after a
suitable transition) the hardcoded code for CVSROOT/history with a
CustomLog directive in CVSROOT/config (inspired by Apache's CustomLog
directive).

For example, getting back the standard behavior would look something like:

StandardHistory=no
CustomLog history checkout "O ${hextime} ${user} - - ${tagdate} ${module}"
CustomLog history rtag-add "T ${hextime} ${user} - A ${tag} ${module}"
CustomLog history rtag-del "T ${hextime} ${user} - D ${tag} ${module}"
. . .

This would also provide a way to log connections and such.

See how apache handles error_log vs. access_log--that is, are they
both on the paradigm of one record per connection attempt?  The
paradigm I'm sketching above is that each CustomLog directive matches
a particular type of event....  What about new types?  Do we want a

CustomLog @var{file} other "${default}"

or something like that?

If so, do we also want:

CustomLog history !rtag-add

(to disable "other" for this case).

The "other" and "!foo" may be unnecessary hair....