You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-cvs@perl.apache.org by st...@apache.org on 2001/11/12 03:44:41 UTC
cvs commit: modperl-docs/src/world/templates choosing.pod
stas 01/11/11 18:44:41
Modified: src/devel/core_explained core_explained.pod
src/devel/modperl_style modperl_style.pod
src/devel/porting_from_1.x porting_from_1.x.pod
src/devel/writing_tests writing_tests.pod
src/user/coding coding.pod
src/user/install install.pod
src/user/intro start_fast.pod
src/world/templates choosing.pod
Log:
use NAME as a header to aid converting
Revision Changes Path
1.4 +4 -2 modperl-docs/src/devel/core_explained/core_explained.pod
Index: core_explained.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/devel/core_explained/core_explained.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- core_explained.pod 2001/09/15 18:49:02 1.3
+++ core_explained.pod 2001/11/12 02:44:40 1.4
@@ -1,5 +1,7 @@
-=head1 mod_perl 2.0 Source Code Explained
+=head1 NAME
+mod_perl 2.0 Source Code Explained
+
=head1 Code Layout
Apache-Test/ - test kit for mod_perl and Apache::* modules
@@ -16,7 +18,7 @@
xs/
-=head1
+=head1 ...
most of the xs/ *.h files have code in them. they are .h because they are
always #include-d, never compiled into their own object file. and only
1.4 +3 -1 modperl-docs/src/devel/modperl_style/modperl_style.pod
Index: modperl_style.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/devel/modperl_style/modperl_style.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- modperl_style.pod 2001/10/02 15:27:02 1.3
+++ modperl_style.pod 2001/11/12 02:44:40 1.4
@@ -1,4 +1,6 @@
-=head1 mod_perl Code Development Style Guide
+=head1 NAME
+
+mod_perl Code Development Style Guide
=head1 Coding Style Guide
1.2 +3 -1 modperl-docs/src/devel/porting_from_1.x/porting_from_1.x.pod
Index: porting_from_1.x.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/devel/porting_from_1.x/porting_from_1.x.pod,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- porting_from_1.x.pod 2001/10/22 06:50:14 1.1
+++ porting_from_1.x.pod 2001/11/12 02:44:40 1.2
@@ -1,4 +1,6 @@
-=head1 Porting Modules from mod_perl 1.x to 2.x
+=head1 NAME
+
+Porting Modules from mod_perl 1.x to 2.x
=head1 Introduction
1.16 +4 -2 modperl-docs/src/devel/writing_tests/writing_tests.pod
Index: writing_tests.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/devel/writing_tests/writing_tests.pod,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- writing_tests.pod 2001/10/23 03:15:56 1.15
+++ writing_tests.pod 2001/11/12 02:44:40 1.16
@@ -1,5 +1,7 @@
-=head1 Developing and Running Tests with the C<Apache::Test> Framework
+=head1 NAME
+Developing and Running Tests with the C<Apache::Test> Framework
+
=head1 Introduction
This chapter is talking about the C<Apache::Test> framework, and in
@@ -1105,7 +1107,7 @@
know that some sub-test is failing but for some reason we want to flag
it as a todo sub-test and not as a broken test. C<Test::Harness>
recognizes I<todo> sub-tests if the standard output line contains the
-substring I< # TODO> after i<not ok> or I<not ok NUMBER> and is
+substring I< # TODO> after I<not ok> or I<not ok NUMBER> and is
counted as a todo sub-test. The text afterwards is the explanation of
the thing that has to be done before this sub-test will succeed. For
example:
1.3 +3 -1 modperl-docs/src/user/coding/coding.pod
Index: coding.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/user/coding/coding.pod,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- coding.pod 2001/10/10 05:26:27 1.2
+++ coding.pod 2001/11/12 02:44:40 1.3
@@ -1,4 +1,6 @@
-=head1 Coding with and for mod_perl
+=head1 NAME
+
+Coding with and for mod_perl
=head1 Prerequisites
1.4 +5 -1 modperl-docs/src/user/install/install.pod
Index: install.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/user/install/install.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- install.pod 2001/09/15 18:49:02 1.3
+++ install.pod 2001/11/12 02:44:41 1.4
@@ -1,6 +1,10 @@
-=head1 Installing mod_perl
+=head1 NAME
+Installing mod_perl
+
=head1 Prerequisites
+
+Lots of prerequisites
=head1 Installing from Source
1.4 +3 -1 modperl-docs/src/user/intro/start_fast.pod
Index: start_fast.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/user/intro/start_fast.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- start_fast.pod 2001/09/15 18:49:02 1.3
+++ start_fast.pod 2001/11/12 02:44:41 1.4
@@ -1,4 +1,6 @@
-=head1 Getting Your Feet Wet with mod_perl
+=head1 NAME
+
+Getting Your Feet Wet with mod_perl
=head1 A Quick Guide to Getting Started with mod_perl
1.4 +3 -1 modperl-docs/src/world/templates/choosing.pod
Index: choosing.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/world/templates/choosing.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- choosing.pod 2001/09/15 18:49:02 1.3
+++ choosing.pod 2001/11/12 02:44:41 1.4
@@ -1,4 +1,6 @@
-=head1 Choosing a Templating System
+=head1 NAME
+
+Choosing a Templating System
=head1 Introduction
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org