> Maybe for tiny fixes it's that easy - for longer contribution where you >> follow development it's not. >> > > How often does that happen (within Commons)? >
Not often enough because then we would have more people working on commons ;) > How often will a new contributor embark in a long rewrite? [And if he > does, how many more newbie "mistakes" will the reviewers need to signal > and correct?] > It's now about a re-write. It's about maintaining local changes until they go upstream. What do you do? Maintain a diff file until then? In Commons Math, I don't remember an issue because of using Subversion. > [And I don't deny that Git is very probably better. But do we really > need the power? If not, I'd prefer not to be _obliged_ to learn it right > now in order to be able to work on CM, just because of a hypothetical > miraculous contributor that would be put off by Subversion.] > "learn" might be a bit of an overstatement ;) If you don't do fancy things there are maybe 6 commands you could write down. For someone working on Commons Math I am sure it should not take that much time get this ;) > Anyway - I'll try not to get sucked into this discussion again. >> Just wanted to state that I think it could be a good thing. >> > > A good thing for those who know how to use Git. Not so good for me. > See above. I bet you are smarter than you are lazy to make it a non-issue :) cheers, Torsten
