head 1.6; access; symbols; locks; strict; comment @# @; 1.6 date 2004.05.06.19.50.03; author openpkg-cvs; state Exp; branches; next 1.5; 1.5 date 2004.05.02.08.50.04; author openpkg-cvs; state Exp; branches; next 1.4; 1.4 date 2004.05.02.08.48.18; author openpkg-cvs; state Exp; branches; next 1.3; 1.3 date 2004.05.02.08.35.31; author openpkg-cvs; state Exp; branches; next 1.2; 1.2 date 2001.08.29.15.27.45; author rse; state Exp; branches; next 1.1; 1.1 date 2001.02.05.11.35.30; author rse; state Exp; branches; next ; desc @@ 1.6 log @ok, break everything by upgrading to the latest OSSP shiela snapshot @ text @# The "loginfo" file controls where "cvs commit" log information # is sent. The first entry on a line is a regular expression which must match # the directory that the change is being made to, relative to the # $CVSROOT. If a match is found, then the remainder of the line is a filter # program that should expect log information on its standard input. # # If the repository name does not match any of the regular expressions in this # file, the "DEFAULT" line is used, if it is specified. # # If the name ALL appears as a regular expression it is always used # in addition to the first matching regex or DEFAULT. # # If any format strings are present in the filter, they will be replaced as # follows: # %p = path relative to repository # %r = repository (path portion of $CVSROOT) # %{sVv} = attribute list = file name, old version number (pre-checkin), # new version number (post-checkin). When either old or new # revision is # unknown, doesn't exist, or isn't applicable, the string "NONE" # will be # placed on the command line instead. # # Note that %{sVv} is a list operator and not all elements are necessary. # Thus %{sv} is # a legal format string, but will only be replaced with file name and new # revision. # it also generates multiple arguments for each file being operated upon. # i.e. if two # files, file1 & file2, are being commited from 1.1 to version 1.1.2.1 and # from 1.1.2.2 # to 1.1.2.3, respectively, %{sVv} will generate the following six arguments # in this # order: file1, 1.1, 1.1.2.1, file2, 1.1.2.2, 1.1.2.3. # # For example: #DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog # or #DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog ALL $CVSROOT/CVSROOT/shiela --hook=loginfo %p %{sVvto} @ 1.5 log @no, seems like the stuff is more complicated @ text @d41 1 a41 1 ALL $CVSROOT/CVSROOT/shiela --hook=loginfo %1{sVvto} @ 1.4 log @try whether this removes the remaining warnings @ text @d41 1 a41 1 ALL $CVSROOT/CVSROOT/shiela --hook=loginfo %{sVvto} @ 1.3 log @switch to new CVS 1.12 format string handling @ text @d41 1 a41 1 ALL $CVSROOT/CVSROOT/shiela --hook=loginfo %1{sVvto} @ 1.2 log @Add Shiela -- CVS Access Control and Logging Facility @ text @d13 10 a22 5 # You may specify a format string as part of the # filter. The string is composed of a `%' followed # by a single format character, or followed by a set of format # characters surrounded by `{' and `}' as separators. The format # characters are: d24 11 a34 3 # s = file name # V = old version number (pre-checkin) # v = new version number (post-checkin) d41 1 a41 1 ALL $CVSROOT/CVSROOT/shiela --hook=loginfo %{sVvto} @ 1.1 log @initial checkin @ text @d27 3 @