[EMAIL PROTECTED] wrote:
Author: pgollucci
Date: Tue Sep 20 12:49:58 2005
New Revision: 290549

URL: http://svn.apache.org/viewcvs?rev=290549&view=rev
Log:
fix bin/build -f

----------------------------------------
File: asf/perl/modperl/docs/trunk/src/docs/1.0/guide/performance.pod
spurious '>' at <input text> line 4779
spurious '>' at <input text> line 4779



Modified:
    perl/modperl/docs/trunk/src/docs/1.0/guide/performance.pod

Modified: perl/modperl/docs/trunk/src/docs/1.0/guide/performance.pod
URL: 
http://svn.apache.org/viewcvs/perl/modperl/docs/trunk/src/docs/1.0/guide/performance.pod?rev=290549&r1=290548&r2=290549&view=diff
==============================================================================
--- perl/modperl/docs/trunk/src/docs/1.0/guide/performance.pod (original)
+++ perl/modperl/docs/trunk/src/docs/1.0/guide/performance.pod Tue Sep 20 
12:49:58 2005
@@ -180,7 +180,7 @@
If you are going to write your own benchmarking utility, use the
 C<Benchmark> module and the C<Time::HiRes> module where you need
-better time precision (<10msec).
+better time precision (less than 10msec).
An example of the C<Benchmark.pm> module usage:

So these two were the cause of the problem? I wonder why we haven't received those "bugs" in first place? It used to work just fine.

--
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://mailchannels.com

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

Reply via email to