> -----Original Message----- > From: Noel Yap [mailto:[EMAIL PROTECTED]] > AFAIK, XP promotes "Refactor early, refactor often." > If so, and given Greg's premise that refactorisation > should be rare and well-thought-out, then CVS isn't > good for within an XP environment. > No, it doesn't mean that. It may mean that Greg shouldn't use XP, but then the XP originators were emphatic that it wasn't the right way to program for everybody. If XP basically requires shuffling files around, then it really won't work well with CVS. If it's a matter of changing the stuff within the files, it should work well. Just commit after each refactor. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
- Re: refactoring when using CVS Greg A. Woods
- Re: refactoring when using CVS Noel Yap
- Re: refactoring when using CVS Greg A. Woods
- Re: refactoring when using CVS Noel Yap
- Re: refactoring when using CVS Noel Yap
- Re: refactoring when using CVS Mark A. Flacy
- Re: refactoring when using CVS Paul Sander
- Re: refactoring when using CVS Noel Yap
- Re: refactoring when using CVS Mark A. Flacy
- Re: refactoring when using CVS Paul Sander
- RE: refactoring when using CVS Thornley, David
- RE: refactoring when using CVS Noel Yap
- RE: refactoring when using CVS Thornley, David
- RE: refactoring when using CVS Noel Yap
- RE: refactoring when using CVS Greg A. Woods
- RE: refactoring when using CVS Noel Yap
- RE: refactoring when using CVS Greg A. Woods
- RE: refactoring when using CVS Noel Yap
- RE: refactoring when using CVS Greg A. Woods
- Re: refactoring when using CVS Thomas S. Urban
- Re: refactoring when using CVS Kaz Kylheku
