(cvs.info.gz) loginfo
Info Catalog
(cvs.info.gz) verifymsg
(cvs.info.gz) Trigger Scripts
(cvs.info.gz) postadmin
C.3.6 Loginfo
-------------
The `loginfo' file is used to control where log information is sent
after versioned changes are made to repository archive files and after
directories are added ot the repository. posttag for how to
log tagging information and postadmin for how to log changes
due to the `admin' command.
The `loginfo' file has the standard form for script hooks (
Trigger Scripts), where each line is a regular expression followed by
a command to execute. It supports the ALL and DEFAULT keywords.
Any specified scripts are called:
`commit'
Once per directory, immediately after a successfully completing
the commit of all files within that directory.
`import'
Once per import, immediately after completion of all write
operations.
`add'
Immediately after the successful `add' of a directory.
Any script called via `loginfo' will be fed the log information on
its standard input. Note that the filter program *must* read *all* of
the log information from its standard input or CVS may fail with a
broken pipe signal.
In addition to the common format strings ( syntax), `loginfo'
supports:
{sVv}
File attributes, where:
s
file name
V
old version number (pre-checkin)
v
new version number (post-checkin)
For example, some valid format strings are `%%', `%s', `%{s}', and
`%{sVv}'.
Currently, if `UseNewInfoFmtStrings' is not set in the `config'
administration file ( config), the format strings will be
substituted as they were in past versions of CVS, but this feature is
deprecated. It is simply in place so that legacy repositories will
remain compatible with the new CVS application. For information on
updating, please see Updating Commit Files.
As an example, if `/u/src/master/yoyodyne/tc' is the repository, `%p'
and `%{sVv}' are the format strings, and three files (ChangeLog,
Makefile, foo.c) were modified, the output might be:
yoyodyne/tc ChangeLog 1.1 1.2 Makefile 1.3 1.4 foo.c 1.12 1.13
Note: when CVS is accessing a remote repository, `loginfo' will be
run on the _remote_ (i.e., server) side, not the client side (
Remote repositories).
Menu
* loginfo example Loginfo example
* Keeping a checked out copy Updating a tree on every checkin
Info Catalog
(cvs.info.gz) verifymsg
(cvs.info.gz) Trigger Scripts
(cvs.info.gz) postadmin
automatically generated byinfo2html