perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ge...@apache.org
Subject cvs commit: modperl-docs/src/docs/2.0/user/help help.pod
Date Wed, 14 Jan 2004 19:45:23 GMT
geoff       2004/01/14 11:45:23

  Modified:    src/docs/1.0/guide help.pod
               src/docs/2.0/user/help help.pod
  Log:
  add pointers to the bug-reporting skeleton
  
  Revision  Changes    Path
  1.27      +10 -0     modperl-docs/src/docs/1.0/guide/help.pod
  
  Index: help.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/help.pod,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- help.pod	28 Aug 2003 01:45:52 -0000	1.26
  +++ help.pod	14 Jan 2004 19:45:23 -0000	1.27
  @@ -127,6 +127,16 @@
   Remember, that if we cannot reproduce the problem, we might not be
   able to solve it.
   
  +To further increase the chances that bugs your code exposes will be
  +investigated, try using C<Apache-Test> to create a self-contained
  +environment that core developers can use to easily reproduce your
  +bug.  To get you started, an C<Apache-Test> bug skeleton has been
  +created:
  +
  +http://perl.apache.org/~geoff/bug-reporting-skeleton-mp1.tar.gz
  +
  +Detailed instructions are contained within the C<README>.
  +
   =over
   
   =item Getting the Backtrace From Core Dumps
  
  
  
  1.27      +9 -0      modperl-docs/src/docs/2.0/user/help/help.pod
  
  Index: help.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/help/help.pod,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- help.pod	25 Aug 2003 07:48:02 -0000	1.26
  +++ help.pod	14 Jan 2004 19:45:23 -0000	1.27
  @@ -123,6 +123,15 @@
   Finally don't forget to copy-n-paste (not type!) the B<relevant> part
   of the I<error_log> file (not the whole file!).
   
  +To further increase the chances that bugs your code exposes will be
  +investigated, try using C<Apache-Test> to create a self-contained
  +test that core developers can easily run.  To get you started,
  +an C<Apache-Test> bug skeleton has been created:
  +
  +http://perl.apache.org/~geoff/bug-reporting-skeleton-mp2.tar.gz
  +
  +Detailed instructions are contained within the C<README>.
  +
   =head2 'C<make test>' Failures
   
   If when running 'make test' some of the tests fail, please re-run them
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org


Mime
View raw message