Jeremy Bennett <[email protected]> writes: > We are rather going down the route of "git is the answer, now how do we > change the question to fit the answer". I use SVN, CVS and git > professionally. They all have their strengths and weaknesses. For every > expert who marvels at the richness of git, there is a beginner baffled > by its complexity. The answer is to use the right tool for each job.
Using git (or any other DVCS) in the same manner as SVN/CVS doesn't introduce any additional complexity. In a sparse team with developers not working just on small patches, a DVCS can make the merge phase a lot easier. I am not sure nowadays there is a single task where CVS can be a better choice than git (except maybe a test-suite for CVS). Cheers, Giuseppe _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
