loginfo 1.7 KB

12345678910111213141516171819202122232425262728293031
  1. # The "loginfo" file controls where "cvs commit" log information
  2. # is sent. The first entry on a line is a regular expression which must match
  3. # the directory that the change is being made to, relative to the
  4. # $CVSROOT. If a match is found, then the remainder of the line is a filter
  5. # program that should expect log information on its standard input.
  6. #
  7. # If the repository name does not match any of the regular expressions in this
  8. # file, the "DEFAULT" line is used, if it is specified.
  9. #
  10. # If the name ALL appears as a regular expression it is always used
  11. # in addition to the first matching regex or DEFAULT.
  12. #
  13. # If any format strings are present in the filter, they will be replaced as follows:
  14. # %p = path relative to repository
  15. # %r = repository (path portion of $CVSROOT)
  16. # %{sVv} = attribute list = file name, old version number (pre-checkin),
  17. # new version number (post-checkin). When either old or new revision is
  18. # unknown, doesn't exist, or isn't applicable, the string "NONE" will be
  19. # placed on the command line instead.
  20. #
  21. # Note that %{sVv} is a list operator and not all elements are necessary. Thus %{sv} is
  22. # a legal format string, but will only be replaced with file name and new revision.
  23. # it also generates multiple arguments for each file being operated upon. i.e. if two
  24. # files, file1 & file2, are being commited from 1.1 to version 1.1.2.1 and from 1.1.2.2
  25. # to 1.1.2.3, respectively, %{sVv} will generate the following six arguments in this
  26. # order: file1, 1.1, 1.1.2.1, file2, 1.1.2.2, 1.1.2.3.
  27. #
  28. # For example:
  29. #DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
  30. # or
  31. #DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog