Shawn Pearce [off-list ref] writes:
Today I was talking with someone that I collaborate with through
Git and they still seemed to not get the idea that all branches
in their repository are local, and that at least a 'git fetch'
is needed to update the local tracking branches to the version
in the central repository that we collaborate through. And this
isn't the first time we've had such discussions.
To me, the biggest difficulty was to understand the vocubulary. I
started with cogito, and looked for branching features in cg-branch-*.
The /features/ themselves seem nice, but the names of commands are
confusing to me. I'd expect something called cg-branch-add to create a
new branch, while it just tells cogito where to find one. And the git
Vs cogito increased the confusion.
--
Matthieu Moy wrote:
Shawn Pearce [off-list ref] writes:
quoted
Today I was talking with someone that I collaborate with through
Git and they still seemed to not get the idea that all branches
in their repository are local, and that at least a 'git fetch'
is needed to update the local tracking branches to the version
in the central repository that we collaborate through. And this
isn't the first time we've had such discussions.
To me, the biggest difficulty was to understand the vocubulary.
I had that same problem, although I started with git and came from CVS /
SVN. I am sufficiently experienced with those two system to hope that I
wouldn't come across any similarities at all, so I wasn't expecting any,
so I didn't get too badly bitten.
The Documentation/glossary.txt file is a very good place to start
reading, although I wouldn't object to it being re-arranged to have the
terms described there pop up "in order of appearance", so to speak. I
sent in a couple of patches to the glossary file whenever I encountered
something in gittish that I didn't understand. Sometimes I had managed
to guess the correct meaning and the patch got applied. In other cases I
had it completely wrong and other, more gittish-fluent, people corrected
the patches and amended the documentation that led to the confusion.
I think this is the only way to keep the docs alive and
newcomer-friendly. Sadly, neither the maintainer nor the active
contributors have newbie-eyes so we're relying on everyone who *are* new
to git to help keep git easy for new people.
And the git Vs cogito increased the confusion.
I've found that too. It's a shame that some things can be done with git
that isn't possible (or at least easy) with cogito and the other way
around. The shared but divergent terminology doesn't exactly help
either. Now I fear it's too late to do anything about it.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se