.TH "cvsgraph.conf" "5" "1.7.0" "B. Stultiens" "CVS/RCS Utilities" .SH "NAME" cvsgraph.conf \- CVS/RCS repository grapher configuration .SH "OVERVIEW" The configuration file is a context free grammar where empty lines and whitespace are ignored. Comments start with '#' and everything until end of line is ignored. .br A configuration parameter is written as: .br = ; .br .LP Keywords are defined in \fBPARAMETERS\fR. The argument can be either numerical or string typed. .LP Numbers may be entered as octal, decimal or hex as in 0117, 79 and 0x4f respectively. Floating point numbers contain a single '.', but must start with a digit. Integer numbers are automagically converted to floats if required. .LP Strings are C\-style strings, enclosed in double quotes in which characters may be escaped with '\\' and written in octal and hex escapes. Note that '\\' must be escaped if it is to be entered as a character. Escapes recognized are '\\[abfnrtv]', '\\[xX][0-9a-fA-F]{2}' and '\\[012][0-7]{0,2}'. .br Some strings are expanded with printf like conversions which start with '%'. Not all are applicable at all times, in which case they will expand to nothing. .br Note that expansions of paths are available with and without trailing '/'. The distinction is required for path construction to ensure that empty expansions will not redirect the path to root and no double '/' in a path is generated. .TP %c CVS root including a trailing '/' if non\-empty .TP %C CVS root without trailing '/', regardless of how it was entered on the command line .TP %m CVS module including trailing '/' if non\-empty .TP %M CVS module without trailing '/', regardless of how it was entered on the command line .TP %f filename without path (\fIbasename \fR functionality) .TP %F filename without path and with ",v" stripped (\fIbasename ,v\fR functionality) .TP %p path part of filename. This includes a trailing '/' if the path is non\-empty .TP %r number of revisions .TP %b number of branches .TP %% literal '%' .TP %R the revision number (e.g. '1.2.4.4') .TP %P previous revision number .TP %B the branch number (e.g. '1.2.4') .TP %d date of revision .TP %a author of revision .TP %s state of revision .TP %l The log entry of the revision. You need to enable \fBparse_logs\fR for this to work. You may append an optional truncate length by writing '[num]' (with num the maximum length) directly after %l. If no truncation is specified, then all will be expanded. Specifying a negative truncation length means that newlines should be replaced by spaces. If truncation occurs, then "..." will be appended. The expansion is scanned for possible HTML entities and are replaced by &#...; equivalents. .br For example: "%l[25]" will expand up to 25 characters of the log. .br Note: This expansion is obsolete. Please use "%(%L%)"; see comment below. .TP %L Same as %l, but no HTML entity translations are performed. .TP %t current tag of branch or revision .TP %0..%9 command\-line argument \-0 .. \-9 .TP %(...%) HTMLize the string withing the parenthesis. This is useful to prevent a possible cross site scripting bug when expanding tags into the map generation. For an exploit, you need to have an attack on your CVS server, or you need to be a complete idiot to enter a tag with '<', '>' or '"' characters. .br Example: a string "%(%t%)", with tag \fB>