git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Did anyone have trouble learning the idea of local vs. remote branches?
Date: Tue, 7 Nov 2006 12:24:50 -0500	[thread overview]
Message-ID: <20061107172450.GA26591@spearce.org> (raw)

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.

It dawned on me that this person still hasn't grasped the idea
behind fetch.  A few other users that I know also have commented on
how difficult fetch is to learn.

Most seemed to think that fetch would update their working directory,
or their current branch, as there is no other way to "download
changes from origin".  They also seem to expect their local tracking
branch to automatically update, especially when invoking
`git checkout -b foo tracking-branch`.


Clearly there is a gap in communicating these ideas in a way that
they can be understood by users.  Of course in at least one case
the users just isn't reading any Git documentation and plows ahead
as though it were CVS ('cause everything's "just like CVS") *sigh*.

-- 

             reply	other threads:[~2006-11-07 17:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 17:24 Shawn Pearce [this message]
2006-11-07 18:08 ` Did anyone have trouble learning the idea of local vs. remote branches? Salikh Zakirov
2006-11-08  6:10   ` Shawn Pearce
2006-11-08  5:19 ` Matthieu Moy
2006-11-08 12:17   ` Andreas Ericsson
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=20061107172450.GA26591@spearce.org \
    --to=spearce@spearce.org \
    --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).