perl-modperl-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a..@hyperreal.org
Subject cvs commit: modperl-site mod_perl_cvs.html
Date Thu, 01 Jul 1999 05:18:58 GMT
ask         99/06/30 22:18:58

  Modified:    .        mod_perl_cvs.html
  Log:
  Sync
  
  Revision  Changes    Path
  1.2       +6 -5      modperl-site/mod_perl_cvs.html
  
  Index: mod_perl_cvs.html
  ===================================================================
  RCS file: /home/cvs/modperl-site/mod_perl_cvs.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- mod_perl_cvs.html	1998/09/10 04:34:59	1.1
  +++ mod_perl_cvs.html	1999/07/01 05:18:57	1.2
  @@ -1,7 +1,7 @@
   <HTML>
   <HEAD>
   <TITLE>mod_perl_cvs - Access to the mod_perl CVS development tree</TITLE>
  -<LINK REV="made" HREF="mailto:ask@balder.netcetera.dk">
  +<LINK REV="made" HREF="mailto:ask@impatience.valueclick.com">
   </HEAD>
   
   <BODY>
  @@ -41,10 +41,11 @@
   version and can help see to it that mod_perl does compile and work on all
   platforms, with the various versions and configurations of Perl and Apache.
   Patches are always welcome, simply testing the latest snapshots is just as,
  -if not more helpful. When you build mod_perl, running 'make test_report'
  -will send a message to the <EM>modperl-cvs@apache.org</EM> list, which is the
same place cvs commit logs and diffs are mailed to. The
  -message sent by test_report includes the output of 'make test', plus
  -version and configuration information for your Perl and Apache.
  +if not more helpful.
  +
  +<P>
  +It's recommended to subscribe to the <EM>modperl-cvs@apache.org</EM> list,
which is the place cvs commit logs and diffs are mailed to; at least
  +if you're going to work on the code.
   
   <P>
   Here are the several ways to access the cvs tree.
  
  
  

Mime
View raw message