From: "Felipe Contreras" <felipe.contre...@gmail.com>
Sent: Saturday, October 19, 2013 3:47 AM
Subject: Re: [git-users] How to list branches
On Fri, Oct 18, 2013 at 9:31 PM, Blake McBride <blake1...@gmail.com>
I now see that the -a list option displays all of the branches. The
names are preceded with remotes/origin. Don't know what that means
is occurring when I check it out (from the local repository) to make
local branch. Again, I am lost. (I come from the subversion world
I don't understand what is so difficult: 'origin/master' means the
'master' branch in the 'origin' repository. To see the URLs of the
remote repositories you can do 'git remote -v'.
As Filipe points out, once you understand the 'Distributed' nature of a
DVCS, this becomes easy. But it han be a hard step to move from the
centralised VCS style. If you are making the step on your own it takes
time, and mistakes, to learn. If you are in the companty of existing
users or fellow learners its much easier.
Importantly there is a shortage of commonly understood of descriptive
(a) A branch that is physically on a remote server
(b) A branch that has been copied across to your machine but is
still marked as being a remote copy (and normally 'hidden', and not
changed by you)
(c) A branch that you have asked to be brought into your viewing,
and that you will edit.
(a) and (b) are both remote branches, with (b) usually being a
Note that centralised VCS has been around since before the Titanic, but
there are only a very few few modern DVCS systems for the e-data age
(where copying is 100% reliable, essentially instantaneous, and 100%
verifiable via crypto checksums)
Also, now that I can see some sort of branches that were created
else and have some sort of other status, how can I tell where these
were off of and what cross branch merges occurred?
Just like you would do with local branches. A command like this
usually does the trick:
git log --oneline --graph --decorate origin/master...master
I have the available three books on git. What would you recommend in
to understand all of the above difficulties?
Why don't you use the link I sent to the ProGit book chapter about
these? It's free.
Read around the discussions as much as possible to help relearn how a
(D)VCS should be operated in the modern world - the Titanic sunk a long
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.