stas        2002/06/15 11:24:58

  Modified:    src/docs/2.0/api/mod_perl-2.0/Apache Reload.pod
  Log:
  use =head1 for non-synopsis things
  
  Revision  Changes    Path
  1.7       +4 -4      
modperl-docs/src/docs/2.0/api/mod_perl-2.0/Apache/Reload.pod
  
  Index: Reload.pod
  ===================================================================
  RCS file: 
/home/cvs/modperl-docs/src/docs/2.0/api/mod_perl-2.0/Apache/Reload.pod,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- Reload.pod        1 Jun 2002 08:53:43 -0000       1.6
  +++ Reload.pod        15 Jun 2002 18:24:58 -0000      1.7
  @@ -116,7 +116,7 @@
   magically reloaded on the next request. This option works with any
   mode described before.
   
  -=head2 Performance Issues
  +=head1 Performance Issues
   
   This modules is perfectly suited for a development environment. Though
   it's possible that you would like to use it in a production
  @@ -145,14 +145,14 @@
   Therefore doing a full server stop and restart is probably a better
   solution.
   
  -=head2 Debug
  +=head1 Debug
   
   If you aren't sure whether the modules that are supposed to be
   reloaded, are actually getting reloaded, turn the debug mode on:
   
     PerlSetVar ReloadDebug On
   
  -=head2 Threaded MPM and Multiple Perl Interpreters
  +=head1 Threaded MPM and Multiple Perl Interpreters
   
   If you use C<Apache::Reload> with a threaded MPM and multiple Perl
   interpreters, the modules will be reloaded by each interpreter as they
  @@ -168,7 +168,7 @@
   reloaded subroutines.
   
   
  -=head2 Pseudo-hashes
  +=head1 Pseudo-hashes
   
   The short summary of this is: Don't use pseudo-hashes. They are
   deprecated since Perl 5.8 and will be removed in 5.10
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to