Possibly helpful: not-on-a-branch is a place you can land partway
through a rebase / merge process.
It can be painful to get your head around the git way of doing things,
if you have already worked with systems that use the CVS-SVN model.
Among other things, you are used to thinking of merge-then-commit, but
with DVCS you generally commit-then-merge (or commit-then-rebase)
instead.
Those conventions are okay. My concern now is not being able to understand
how pull updates the working directory, when most definitions of the command
seem to say that the update it causes stops at the repo (the compressed data
in the .git directory). I found one definition that seems to imply that the
working directory was updated too, not just the repo. Checkout seems to be
the only command that explicitly states that the working directory can be
changed by the command. I think I'm missing some important connection
between the local branches and the remote-tracking branches they track.
It is generally easier if you start with a tiny sample project, and
work through various scenarios, rather than learn Git in the middle of
a not-tiny project.
http://nathanj.github.com/gitguide/tour.html
Shaping
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
