From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: Did anyone have trouble learning the idea of local vs. remote branches?
Date: Wed, 08 Nov 2006 13:17:59 +0100 [thread overview]
Message-ID: <4551CAF7.3050008@op5.se> (raw)
In-Reply-To: <vpqbqnisegc.fsf@ecrins.imag.fr>
Matthieu Moy wrote:
> Shawn Pearce <spearce@spearce.org> 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 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
next prev parent reply other threads:[~2006-11-08 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 17:24 Did anyone have trouble learning the idea of local vs. remote branches? Shawn Pearce
2006-11-07 18:08 ` Salikh Zakirov
2006-11-08 6:10 ` Shawn Pearce
2006-11-08 5:19 ` Matthieu Moy
2006-11-08 12:17 ` Andreas Ericsson [this message]
2006-11-08 5:23 ` Wink Saville
2006-11-08 7:29 ` Jakub Narebski
2006-11-08 16:40 ` Wink Saville
2006-11-08 17:36 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4551CAF7.3050008@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).