--- shiela.pod 2002/12/22 11:06:50 1.9
+++ shiela.pod 2002/12/22 11:10:43 1.10
@@ -8,8 +8,8 @@
## which can be found at http://www.ossp.org/pkg/tool/shiela/.
##
## This program is free software; you can redistribute it and/or
-## modify it under the terms of the GNU General Public License
-## as published by the Free Software Foundation; either version
+## modify it under the terms of the GNU General Public License
+## as published by the Free Software Foundation; either version
## 2.0 of the License, or (at your option) any later version.
##
## This program is distributed in the hope that it will be useful,
@@ -17,7 +17,7 @@
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
-## You should have received a copy of the GNU General Public License
+## You should have received a copy of the GNU General Public License
## along with this file; if not, write to the Free Software
## Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
## USA, or contact Ralf S. Engelschall <rse@engelschall.com>.
@@ -25,7 +25,7 @@
## shiela.pod: manual page (syntax: POD)
##
-=pod
+=pod
=head1 NAME
@@ -274,7 +274,7 @@
=item B<Path E<lt>pathE<gt>;>
-The filesystem path on the repository host under which the repository resides.
+The filesystem path on the repository host under which the repository resides.
This usually is equal to the C<$CVSROOT> variable.
Example: C<Path /e/foo/cvs;>
@@ -299,7 +299,7 @@
This defines an access control list for
C<$CVSROOT/>E<lt>modulepathE<gt>/E<lt>filepathE<gt>. It ensures that a
repository operation to this path can only be done by the specified
-users/groups.
+users/groups.
The argument E<lt>filepathE<gt> can be either a full path (e.g.
"C<subdir1/subdir2/file>"), or a shell wildcard pattern (e.g.
@@ -328,7 +328,7 @@
The occurance of the logging message depends how the specified report is
defined (by C<Report>). After it is produced it is send to E<lt>targetE<gt>
which can be either an Email address of the form I<user>C<@>I<domain> or a
-filesystem path.
+filesystem path.
Example: C<Log * mail:foo-cvs@foo.dom file:CVSROOT/commit.log;>
@@ -342,7 +342,7 @@
Logging {
Reports {
Report <reportid> {
- Content <contentid> [...];
+ Content <contentid> [...];
[Details <type>:<arg>;]
[Prefix <string>;]
};
@@ -364,10 +364,10 @@
This defines the report contents and contents order. That is the contents is
created top to bottom by concatenating one or more content blocks which are
-specified by one or more E<lt>contentidE<gt> arguments.
+specified by one or more E<lt>contentidE<gt> arguments.
-The available content blocks are:
-C<title>: a two line title header,
+The available content blocks are:
+C<title>: a two line title header,
C<rule>: a horizontal rule,
C<header>: a four line repository and user summary header,
C<files>: a table of added/modified/removed/touched files,
@@ -394,7 +394,7 @@
=item B<Prefix E<lt>stringE<gt>;>
-This configures that every line of the generated report message is
+This configures that every line of the generated report message is
prefixed with E<lt>stringE<gt>.
Example: C<Prefix " ";>
@@ -518,7 +518,7 @@
=item B<http://www.ossp.org/pkg/tool/shiela/>
-Here you can find the official B<OSSP shiela> homepage.
+Here you can find the official B<OSSP shiela> homepage.
=item B<http://cvs.ossp.org/pkg/tool/shiela/>
|
