Steve Hay wrote:
Gisle Aas wrote:


Steve Hay <[EMAIL PROTECTED]> writes:




Gisle Aas wrote:




I had to do tests with an older version of mod_perl_1.99 that still
had the perl/ithreads* tests.  I see that these tests was removed from
the distribution in [1], but I think that if you apply the attached
patch you can start distribution these tests again.

[1] 
http://cvs.apache.org/viewcvs.cgi/modperl-2.0/lib/ModPerl/Manifest.pm?r1=1.9&r2=1.10




mp2 is now in svn, not cvs.



Isn't CVS in sync as well?

I read <http://perl.apache.org/contribute/> and it only mentioned CVS
and had a pointer to the CVS web interface.




Check-out the latest svn revision as described at:

http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution



This one also has pointers to the CVS snapshots and the CVS web interface so I assume that it is kept in sync.



Other people can say for sure whether cvs is kept in sync, but my impression was that it was not. I could be wrong. Anyway, svn is definitely the way forward.

It's not in sync. The only reason it's still working is because I have tons of unfinished cvs checkouts, which I need to find the time to process and then we can close cvs.


I know that not all the docs have been updated yet, hence there are various references to cvs around the place still.

Right, sorry, I'll be updating those pages today. for now please refer to: http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution which is up-to-date.

--
__________________________________________________________________
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://ticketmaster.com

--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to