/[pcre]/code/trunk/doc/html/pcregrep.html
ViewVC logotype

Diff of /code/trunk/doc/html/pcregrep.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 453 by ph10, Fri Sep 18 19:12:35 2009 UTC revision 654 by ph10, Tue Aug 2 11:00:40 2011 UTC
# Line 74  possible to search for patterns that spa Line 74  possible to search for patterns that spa
74  boundary is controlled by the <b>-N</b> (<b>--newline</b>) option.  boundary is controlled by the <b>-N</b> (<b>--newline</b>) option.
75  </P>  </P>
76  <P>  <P>
77  Patterns are limited to 8K or BUFSIZ characters, whichever is the greater.  The amount of memory used for buffering files that are being scanned is
78  BUFSIZ is defined in <b>&#60;stdio.h&#62;</b>. When there is more than one pattern  controlled by a parameter that can be set by the <b>--buffer-size</b> option.
79  (specified by the use of <b>-e</b> and/or <b>-f</b>), each pattern is applied to  The default value for this parameter is specified when <b>pcregrep</b> is built,
80  each line in the order in which they are defined, except that all the <b>-e</b>  with the default default being 20K. A block of memory three times this size is
81  patterns are tried before the <b>-f</b> patterns.  used (to allow for buffering "before" and "after" lines). An error occurs if a
82    line overflows the buffer.
83    </P>
84    <P>
85    Patterns are limited to 8K or BUFSIZ bytes, whichever is the greater. BUFSIZ is
86    defined in <b>&#60;stdio.h&#62;</b>. When there is more than one pattern (specified by
87    the use of <b>-e</b> and/or <b>-f</b>), each pattern is applied to each line in
88    the order in which they are defined, except that all the <b>-e</b> patterns are
89    tried before the <b>-f</b> patterns.
90  </P>  </P>
91  <P>  <P>
92  By default, as soon as one pattern matches (or fails to match when <b>-v</b> is  By default, as soon as one pattern matches (or fails to match when <b>-v</b> is
# Line 119  standard input is always so treated. Line 127  standard input is always so treated.
127  </P>  </P>
128  <br><a name="SEC4" href="#TOC1">OPTIONS</a><br>  <br><a name="SEC4" href="#TOC1">OPTIONS</a><br>
129  <P>  <P>
130  The order in which some of the options appear can affect the output. For  The order in which some of the options appear can affect the output. For
131  example, both the <b>-h</b> and <b>-l</b> options affect the printing of file  example, both the <b>-h</b> and <b>-l</b> options affect the printing of file
132  names. Whichever comes later in the command line will be the one that takes  names. Whichever comes later in the command line will be the one that takes
133  effect.  effect. Numerical values for options may be followed by K or M, to signify
134    multiplication by 1024 or 1024*1024 respectively.
135  </P>  </P>
136  <P>  <P>
137  <b>--</b>  <b>--</b>
138  This terminate the list of options. It is useful if the next item on the  This terminates the list of options. It is useful if the next item on the
139  command line starts with a hyphen but is not an option. This allows for the  command line starts with a hyphen but is not an option. This allows for the
140  processing of patterns and filenames that start with hyphens.  processing of patterns and filenames that start with hyphens.
141  </P>  </P>
# Line 149  of <i>number</i> is expected to be relat Line 158  of <i>number</i> is expected to be relat
158  guarantees to have up to 8K of preceding text available for context output.  guarantees to have up to 8K of preceding text available for context output.
159  </P>  </P>
160  <P>  <P>
161    <b>--buffer-size=</b><i>number</i>
162    Set the parameter that controls how much memory is used for buffering files
163    that are being scanned.
164    </P>
165    <P>
166  <b>-C</b> <i>number</i>, <b>--context=</b><i>number</i>  <b>-C</b> <i>number</i>, <b>--context=</b><i>number</i>
167  Output <i>number</i> lines of context both before and after each matching line.  Output <i>number</i> lines of context both before and after each matching line.
168  This is equivalent to setting both <b>-A</b> and <b>-B</b> to the same value.  This is equivalent to setting both <b>-A</b> and <b>-B</b> to the same value.
# Line 178  coloured. The value (which is optional, Line 192  coloured. The value (which is optional,
192  connected to a terminal. More resources are used when colouring is enabled,  connected to a terminal. More resources are used when colouring is enabled,
193  because <b>pcregrep</b> has to search for all possible matches in a line, not  because <b>pcregrep</b> has to search for all possible matches in a line, not
194  just one, in order to colour them all.  just one, in order to colour them all.
195  </P>  <br>
196  <P>  <br>
197  The colour that is used can be specified by setting the environment variable  The colour that is used can be specified by setting the environment variable
198  PCREGREP_COLOUR or PCREGREP_COLOR. The value of this variable should be a  PCREGREP_COLOUR or PCREGREP_COLOR. The value of this variable should be a
199  string of two numbers, separated by a semicolon. They are copied directly into  string of two numbers, separated by a semicolon. They are copied directly into
# Line 224  that matched. Line 238  that matched.
238  When <b>pcregrep</b> is searching the files in a directory as a consequence of  When <b>pcregrep</b> is searching the files in a directory as a consequence of
239  the <b>-r</b> (recursive search) option, any regular files whose names match the  the <b>-r</b> (recursive search) option, any regular files whose names match the
240  pattern are excluded. Subdirectories are not excluded by this option; they are  pattern are excluded. Subdirectories are not excluded by this option; they are
241  searched recursively, subject to the <b>--exclude_dir</b> and  searched recursively, subject to the <b>--exclude-dir</b> and
242  <b>--include_dir</b> options. The pattern is a PCRE regular expression, and is  <b>--include_dir</b> options. The pattern is a PCRE regular expression, and is
243  matched against the final component of the file name (not the entire path). If  matched against the final component of the file name (not the entire path). If
244  a file name matches both <b>--include</b> and <b>--exclude</b>, it is excluded.  a file name matches both <b>--include</b> and <b>--exclude</b>, it is excluded.
245  There is no short form for this option.  There is no short form for this option.
246  </P>  </P>
247  <P>  <P>
248  <b>--exclude_dir</b>=<i>pattern</i>  <b>--exclude-dir</b>=<i>pattern</i>
249  When <b>pcregrep</b> is searching the contents of a directory as a consequence  When <b>pcregrep</b> is searching the contents of a directory as a consequence
250  of the <b>-r</b> (recursive search) option, any subdirectories whose names match  of the <b>-r</b> (recursive search) option, any subdirectories whose names match
251  the pattern are excluded. (Note that the \fP--exclude\fP option does not affect  the pattern are excluded. (Note that the \fP--exclude\fP option does not affect
252  subdirectories.) The pattern is a PCRE regular expression, and is matched  subdirectories.) The pattern is a PCRE regular expression, and is matched
253  against the final component of the name (not the entire path). If a  against the final component of the name (not the entire path). If a
254  subdirectory name matches both <b>--include_dir</b> and <b>--exclude_dir</b>, it  subdirectory name matches both <b>--include-dir</b> and <b>--exclude-dir</b>, it
255  is excluded. There is no short form for this option.  is excluded. There is no short form for this option.
256  </P>  </P>
257  <P>  <P>
# Line 299  Ignore upper/lower case distinctions dur Line 313  Ignore upper/lower case distinctions dur
313  When <b>pcregrep</b> is searching the files in a directory as a consequence of  When <b>pcregrep</b> is searching the files in a directory as a consequence of
314  the <b>-r</b> (recursive search) option, only those regular files whose names  the <b>-r</b> (recursive search) option, only those regular files whose names
315  match the pattern are included. Subdirectories are always included and searched  match the pattern are included. Subdirectories are always included and searched
316  recursively, subject to the \fP--include_dir\fP and <b>--exclude_dir</b>  recursively, subject to the \fP--include-dir\fP and <b>--exclude-dir</b>
317  options. The pattern is a PCRE regular expression, and is matched against the  options. The pattern is a PCRE regular expression, and is matched against the
318  final component of the file name (not the entire path). If a file name matches  final component of the file name (not the entire path). If a file name matches
319  both <b>--include</b> and <b>--exclude</b>, it is excluded. There is no short  both <b>--include</b> and <b>--exclude</b>, it is excluded. There is no short
320  form for this option.  form for this option.
321  </P>  </P>
322  <P>  <P>
323  <b>--include_dir</b>=<i>pattern</i>  <b>--include-dir</b>=<i>pattern</i>
324  When <b>pcregrep</b> is searching the contents of a directory as a consequence  When <b>pcregrep</b> is searching the contents of a directory as a consequence
325  of the <b>-r</b> (recursive search) option, only those subdirectories whose  of the <b>-r</b> (recursive search) option, only those subdirectories whose
326  names match the pattern are included. (Note that the <b>--include</b> option  names match the pattern are included. (Note that the <b>--include</b> option
327  does not affect subdirectories.) The pattern is a PCRE regular expression, and  does not affect subdirectories.) The pattern is a PCRE regular expression, and
328  is matched against the final component of the name (not the entire path). If a  is matched against the final component of the name (not the entire path). If a
329  subdirectory name matches both <b>--include_dir</b> and <b>--exclude_dir</b>, it  subdirectory name matches both <b>--include-dir</b> and <b>--exclude-dir</b>, it
330  is excluded. There is no short form for this option.  is excluded. There is no short form for this option.
331  </P>  </P>
332  <P>  <P>
# Line 326  output once, on a separate line. Line 340  output once, on a separate line.
340  Instead of outputting lines from the files, just output the names of the files  Instead of outputting lines from the files, just output the names of the files
341  containing lines that would have been output. Each file name is output  containing lines that would have been output. Each file name is output
342  once, on a separate line. Searching normally stops as soon as a matching line  once, on a separate line. Searching normally stops as soon as a matching line
343  is found in a file. However, if the <b>-c</b> (count) option is also used,  is found in a file. However, if the <b>-c</b> (count) option is also used,
344  matching continues in order to obtain the correct count, and those files that  matching continues in order to obtain the correct count, and those files that
345  have at least one match are listed along with their counts. Using this option  have at least one match are listed along with their counts. Using this option
346  with <b>-c</b> is a way of suppressing the listing of files with no matches.  with <b>-c</b> is a way of suppressing the listing of files with no matches.
347  </P>  </P>
348  <P>  <P>
# Line 338  are being output. If not supplied, "(sta Line 352  are being output. If not supplied, "(sta
352  short form for this option.  short form for this option.
353  </P>  </P>
354  <P>  <P>
355    <b>--line-buffered</b>
356    When this option is given, input is read and processed line by line, and the
357    output is flushed after each write. By default, input is read in large chunks,
358    unless <b>pcregrep</b> can determine that it is reading from a terminal (which
359    is currently possible only in Unix environments). Output to terminal is
360    normally automatically flushed by the operating system. This option can be
361    useful when the input or output is attached to a pipe and you do not want
362    <b>pcregrep</b> to buffer up large amounts of data. However, its use will affect
363    performance, and the <b>-M</b> (multiline) option ceases to work.
364    </P>
365    <P>
366  <b>--line-offsets</b>  <b>--line-offsets</b>
367  Instead of showing lines or parts of lines that match, show each match as a  Instead of showing lines or parts of lines that match, show each match as a
368  line number, the offset from the start of the line, and a length. The line  line number, the offset from the start of the line, and a length. The line
# Line 355  locale is specified, the PCRE library's Line 380  locale is specified, the PCRE library's
380  used. There is no short form for this option.  used. There is no short form for this option.
381  </P>  </P>
382  <P>  <P>
383    <b>--match-limit</b>=<i>number</i>
384    Processing some regular expression patterns can require a very large amount of
385    memory, leading in some cases to a program crash if not enough is available.
386    Other patterns may take a very long time to search for all possible matching
387    strings. The <b>pcre_exec()</b> function that is called by <b>pcregrep</b> to do
388    the matching has two parameters that can limit the resources that it uses.
389    <br>
390    <br>
391    The <b>--match-limit</b> option provides a means of limiting resource usage
392    when processing patterns that are not going to match, but which have a very
393    large number of possibilities in their search trees. The classic example is a
394    pattern that uses nested unlimited repeats. Internally, PCRE uses a function
395    called <b>match()</b> which it calls repeatedly (sometimes recursively). The
396    limit set by <b>--match-limit</b> is imposed on the number of times this
397    function is called during a match, which has the effect of limiting the amount
398    of backtracking that can take place.
399    <br>
400    <br>
401    The <b>--recursion-limit</b> option is similar to <b>--match-limit</b>, but
402    instead of limiting the total number of times that <b>match()</b> is called, it
403    limits the depth of recursive calls, which in turn limits the amount of memory
404    that can be used. The recursion depth is a smaller number than the total number
405    of calls, because not all calls to <b>match()</b> are recursive. This limit is
406    of use only if it is set smaller than <b>--match-limit</b>.
407    <br>
408    <br>
409    There are no short forms for these options. The default settings are specified
410    when the PCRE library is compiled, with the default default being 10 million.
411    </P>
412    <P>
413  <b>-M</b>, <b>--multiline</b>  <b>-M</b>, <b>--multiline</b>
414  Allow patterns to match more than one line. When this option is given, patterns  Allow patterns to match more than one line. When this option is given, patterns
415  may usefully contain literal newline characters and internal occurrences of ^  may usefully contain literal newline characters and internal occurrences of ^
416  and $ characters. The output for any one match may consist of more than one  and $ characters. The output for a successful match may consist of more than
417  line. When this option is set, the PCRE library is called in "multiline" mode.  one line, the last of which is the one in which the match ended. If the matched
418    string ends with a newline sequence the output ends at the end of that line.
419    <br>
420    <br>
421    When this option is set, the PCRE library is called in "multiline" mode.
422  There is a limit to the number of lines that can be matched, imposed by the way  There is a limit to the number of lines that can be matched, imposed by the way
423  that <b>pcregrep</b> buffers the input file as it scans it. However,  that <b>pcregrep</b> buffers the input file as it scans it. However,
424  <b>pcregrep</b> ensures that at least 8K characters or the rest of the document  <b>pcregrep</b> ensures that at least 8K characters or the rest of the document
425  (whichever is the shorter) are available for forward matching, and similarly  (whichever is the shorter) are available for forward matching, and similarly
426  the previous 8K characters (or all the previous characters, if fewer than 8K)  the previous 8K characters (or all the previous characters, if fewer than 8K)
427  are guaranteed to be available for lookbehind assertions.  are guaranteed to be available for lookbehind assertions. This option does not
428    work when input is read line by line (see \fP--line-buffered\fP.)
429  </P>  </P>
430  <P>  <P>
431  <b>-N</b> <i>newline-type</i>, <b>--newline=</b><i>newline-type</i>  <b>-N</b> <i>newline-type</i>, <b>--newline</b>=<i>newline-type</i>
432  The PCRE library supports five different conventions for indicating  The PCRE library supports five different conventions for indicating
433  the ends of lines. They are the single-character sequences CR (carriage return)  the ends of lines. They are the single-character sequences CR (carriage return)
434  and LF (linefeed), the two-character sequence CRLF, an "anycrlf" convention,  and LF (linefeed), the two-character sequence CRLF, an "anycrlf" convention,
435  which recognizes any of the preceding three types, and an "any" convention, in  which recognizes any of the preceding three types, and an "any" convention, in
436  which any Unicode line ending sequence is assumed to end a line. The Unicode  which any Unicode line ending sequence is assumed to end a line. The Unicode
437  sequences are the three just mentioned, plus VT (vertical tab, U+000B), FF  sequences are the three just mentioned, plus VT (vertical tab, U+000B), FF
438  (formfeed, U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and  (form feed, U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and
439  PS (paragraph separator, U+2029).  PS (paragraph separator, U+2029).
440  <br>  <br>
441  <br>  <br>
# Line 397  output, it precedes the line number. Thi Line 457  output, it precedes the line number. Thi
457  </P>  </P>
458  <P>  <P>
459  <b>-o</b>, <b>--only-matching</b>  <b>-o</b>, <b>--only-matching</b>
460  Show only the part of the line that matched a pattern. In this mode, no  Show only the part of the line that matched a pattern instead of the whole
461  context is shown. That is, the <b>-A</b>, <b>-B</b>, and <b>-C</b> options are  line. In this mode, no context is shown. That is, the <b>-A</b>, <b>-B</b>, and
462  ignored. If there is more than one match in a line, each of them is shown  <b>-C</b> options are ignored. If there is more than one match in a line, each
463  separately. If <b>-o</b> is combined with <b>-v</b> (invert the sense of the  of them is shown separately. If <b>-o</b> is combined with <b>-v</b> (invert the
464  match to find non-matching lines), no output is generated, but the return code  sense of the match to find non-matching lines), no output is generated, but the
465  is set appropriately. This option is mutually exclusive with  return code is set appropriately. If the matched portion of the line is empty,
466  <b>--file-offsets</b> and <b>--line-offsets</b>.  nothing is output unless the file name or line number are being printed, in
467    which case they are shown on an otherwise empty line. This option is mutually
468    exclusive with <b>--file-offsets</b> and <b>--line-offsets</b>.
469    </P>
470    <P>
471    <b>-o</b><i>number</i>, <b>--only-matching</b>=<i>number</i>
472    Show only the part of the line that matched the capturing parentheses of the
473    given number. Up to 32 capturing parentheses are supported. Because these
474    options can be given without an argument (see above), if an argument is
475    present, it must be given in the same shell item, for example, -o3 or
476    --only-matching=2. The comments given for the non-argument case above also
477    apply to this case. If the specified capturing parentheses do not exist in the
478    pattern, or were not set in the match, nothing is output unless the file name
479    or line number are being printed.
480  </P>  </P>
481  <P>  <P>
482  <b>-q</b>, <b>--quiet</b>  <b>-q</b>, <b>--quiet</b>
# Line 419  immediate end-of-file. This option is a Line 492  immediate end-of-file. This option is a
492  option to "recurse".  option to "recurse".
493  </P>  </P>
494  <P>  <P>
495    <b>--recursion-limit</b>=<i>number</i>
496    See <b>--match-limit</b> above.
497    </P>
498    <P>
499  <b>-s</b>, <b>--no-messages</b>  <b>-s</b>, <b>--no-messages</b>
500  Suppress error messages about non-existent or unreadable files. Such files are  Suppress error messages about non-existent or unreadable files. Such files are
501  quietly skipped. However, the return code is still 2, even if matches were  quietly skipped. However, the return code is still 2, even if matches were
# Line 470  convert this to an appropriate sequence Line 547  convert this to an appropriate sequence
547  </P>  </P>
548  <br><a name="SEC7" href="#TOC1">OPTIONS COMPATIBILITY</a><br>  <br><a name="SEC7" href="#TOC1">OPTIONS COMPATIBILITY</a><br>
549  <P>  <P>
550  The majority of short and long forms of <b>pcregrep</b>'s options are the same  Many of the short and long forms of <b>pcregrep</b>'s options are the same
551  as in the GNU <b>grep</b> program. Any long option of the form  as in the GNU <b>grep</b> program (version 2.5.4). Any long option of the form
552  <b>--xxx-regexp</b> (GNU terminology) is also available as <b>--xxx-regex</b>  <b>--xxx-regexp</b> (GNU terminology) is also available as <b>--xxx-regex</b>
553  (PCRE terminology). However, the <b>--locale</b>, <b>-M</b>, <b>--multiline</b>,  (PCRE terminology). However, the <b>--file-offsets</b>, <b>--include-dir</b>,
554  <b>-u</b>, and <b>--utf-8</b> options are specific to <b>pcregrep</b>. If both the  <b>--line-offsets</b>, <b>--locale</b>, <b>--match-limit</b>, <b>-M</b>,
555  <b>-c</b> and <b>-l</b> options are given, GNU grep lists only file names,  <b>--multiline</b>, <b>-N</b>, <b>--newline</b>, <b>--recursion-limit</b>,
556    <b>-u</b>, and <b>--utf-8</b> options are specific to <b>pcregrep</b>, as is the
557    use of the <b>--only-matching</b> option with a capturing parentheses number.
558    </P>
559    <P>
560    Although most of the common options work the same way, a few are different in
561    <b>pcregrep</b>. For example, the <b>--include</b> option's argument is a glob
562    for GNU <b>grep</b>, but a regular expression for <b>pcregrep</b>. If both the
563    <b>-c</b> and <b>-l</b> options are given, GNU grep lists only file names,
564  without counts, but <b>pcregrep</b> gives the counts.  without counts, but <b>pcregrep</b> gives the counts.
565  </P>  </P>
566  <br><a name="SEC8" href="#TOC1">OPTIONS WITH DATA</a><br>  <br><a name="SEC8" href="#TOC1">OPTIONS WITH DATA</a><br>
567  <P>  <P>
568  There are four different ways in which an option with data can be specified.  There are four different ways in which an option with data can be specified.
569  If a short form option is used, the data may follow immediately, or in the next  If a short form option is used, the data may follow immediately, or (with one
570  command line item. For example:  exception) in the next command line item. For example:
571  <pre>  <pre>
572    -f/some/file    -f/some/file
573    -f /some/file    -f /some/file
574  </pre>  </pre>
575    The exception is the <b>-o</b> option, which may appear with or without data.
576    Because of this, if data is present, it must follow immediately in the same
577    item, for example -o3.
578    </P>
579    <P>
580  If a long form option is used, the data may appear in the same command line  If a long form option is used, the data may appear in the same command line
581  item, separated by an equals character, or (with one exception) it may appear  item, separated by an equals character, or (with two exceptions) it may appear
582  in the next command line item. For example:  in the next command line item. For example:
583  <pre>  <pre>
584    --file=/some/file    --file=/some/file
# Line 500  separate the file name from the option, Line 590  separate the file name from the option,
590  specially unless it is at the start of an item.  specially unless it is at the start of an item.
591  </P>  </P>
592  <P>  <P>
593  The exception to the above is the <b>--colour</b> (or <b>--color</b>) option,  The exceptions to the above are the <b>--colour</b> (or <b>--color</b>) and
594  for which the data is optional. If this option does have data, it must be given  <b>--only-matching</b> options, for which the data is optional. If one of these
595  in the first form, using an equals character. Otherwise it will be assumed that  options does have data, it must be given in the first form, using an equals
596  it has no data.  character. Otherwise <b>pcregrep</b> will assume that it has no data.
597  </P>  </P>
598  <br><a name="SEC9" href="#TOC1">MATCHING ERRORS</a><br>  <br><a name="SEC9" href="#TOC1">MATCHING ERRORS</a><br>
599  <P>  <P>
# Line 515  in these circumstances. If this happens, Line 605  in these circumstances. If this happens,
605  message and the line that caused the problem to the standard error stream. If  message and the line that caused the problem to the standard error stream. If
606  there are more than 20 such errors, <b>pcregrep</b> gives up.  there are more than 20 such errors, <b>pcregrep</b> gives up.
607  </P>  </P>
608    <P>
609    The <b>--match-limit</b> option of <b>pcregrep</b> can be used to set the overall
610    resource limit; there is a second option called <b>--recursion-limit</b> that
611    sets a limit on the amount of memory (usually stack) that is used (see the
612    discussion of these options above).
613    </P>
614  <br><a name="SEC10" href="#TOC1">DIAGNOSTICS</a><br>  <br><a name="SEC10" href="#TOC1">DIAGNOSTICS</a><br>
615  <P>  <P>
616  Exit status is 0 if any matches were found, 1 if no matches were found, and 2  Exit status is 0 if any matches were found, 1 if no matches were found, and 2
617  for syntax errors and non-existent or inacessible files (even if matches were  for syntax errors, overlong lines, non-existent or inaccessible files (even if
618  found in other files) or too many matching errors. Using the <b>-s</b> option to  matches were found in other files) or too many matching errors. Using the
619  suppress error messages about inaccessble files does not affect the return  <b>-s</b> option to suppress error messages about inaccessible files does not
620  code.  affect the return code.
621  </P>  </P>
622  <br><a name="SEC11" href="#TOC1">SEE ALSO</a><br>  <br><a name="SEC11" href="#TOC1">SEE ALSO</a><br>
623  <P>  <P>
# Line 538  Cambridge CB2 3QH, England. Line 634  Cambridge CB2 3QH, England.
634  </P>  </P>
635  <br><a name="SEC13" href="#TOC1">REVISION</a><br>  <br><a name="SEC13" href="#TOC1">REVISION</a><br>
636  <P>  <P>
637  Last updated: 13 September 2009  Last updated: 30 July 2011
638  <br>  <br>
639  Copyright &copy; 1997-2009 University of Cambridge.  Copyright &copy; 1997-2011 University of Cambridge.
640  <br>  <br>
641  <p>  <p>
642  Return to the <a href="index.html">PCRE index page</a>.  Return to the <a href="index.html">PCRE index page</a>.

Legend:
Removed from v.453  
changed lines
  Added in v.654

  ViewVC Help
Powered by ViewVC 1.1.5