El 19/10/2010, a las 09:48, Miles Bader escribió: > On Tue, Oct 19, 2010 at 4:19 PM, Wincent Colaiuta <win@xxxxxxxxxxx> wrote: >> We should smooth out these road-bumps (in so far as we can, with respect to backward compatibility and such) rather than just hand-waving them away saying that they are a natural consequence of demolishing the CVS world view and replacing it with something better. That's not true at all; mistakes _were_ made with the terminology, and unfortunately we have to live with some of them because they can't be changed in a non-breaking way, but the changes that we _can_ make to remove the confusion, we should make them. > > Sure, I'm not claiming that git's perfect or can't be improved. [As I > noted, I have my own list of complaints about its terminology.] > > However, just as it's wrong to ignore all complaints for such reasons, > it's _equally_ wrong to assume the opposite and think that all such > complaints are justified. Some differences in terminology _are_ due > to a very different model, and can't simply be papered over. It isn't > "hand-waving" to point this out. They might (and should) be better > documented/explained, but there are definitely terms and concepts > where the only reasonable solution is for newbies to have some > patience and take some time to learn them. Well, I'm not "assuming" that the complaints are justified; I'm talking from 3.5 years of personal experience using Git: - the concept of the "index": learnt it in 30 seconds, and sick of hearing people complain about it - terminology related to concepts of "tracking"/"remote(s)": discomfort almost every time I've had to deal with it gitglossary(7) helps, but no matter how good it is you'll still get confusion unless the terminology is used consistently across the board. Some of this is not actually Git's fault, as a lot of the misuse/abuse of terminology actually comes from people writing blog posts and presentations and not being disciplined about their use of language -- before you know it Google returns mostly garbage results and "the community" ends up speaking a corrupted version of the language -- but the stuff that is within the scope of the Git project itself (man pages, official docs, interfaces) really needs to be top notch. Cheers, Wincent -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html