Ummm think about it... for CVSROOT changes that would mean being easily
able to get a mirror of the project cvs files  (the blah.java,v files),
which AFAIK sourceforge does not enable.

Perhaps a more doable alternative is a list of what to check after CVSROOT
changes.

david jencks

On 2002.10.08 12:33:30 -0400 Tom Coleman wrote:
> 
> Why don't we set up a CVS testbed somewhere to test CVS changes?
> 
> You (editorial 'you') don't (shouldn't) commit changes to code without
> thorough testing.  Considering what's at risk, it seems to me that CVS 
> changes should be made even more cautiously.
> 
> This project already has too many 'moving targets' to try to deal with.
> 
> >
> > I have to modify CVSROOT/modules to test, so please be patient if
> > something does not function.  I will make sure that all jboss-*
> projects
> > function by the days end.
> > 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to