Thank you very much for the help!  I have that book.  I think I'll some 
reading.  My mind is so SVN oriented that when I read the books I keep 
thinking 'but how would I do x?  y?  Z?'  Perhaps x, y, and z don't make 
sense with this new model.

>From what you are saying, I gather that branches created remotely are kept 
noted as such (even though I have a local copy).  When I check the branch 
out, it becomes a totally new local branch.

Thanks for the help!


On Friday, October 18, 2013 9:47:10 PM UTC-5, Felipe Contreras wrote:
> On Fri, Oct 18, 2013 at 9:31 PM, Blake McBride 
> <<javascript:>> 
> wrote: 
> > I now see that the -a list option displays all of the branches.  The 
> branch 
> > names are preceded with remotes/origin.  Don't know what that means or 
> what 
> > is occurring when I check it out (from the local repository) to make it 
> a 
> > local branch.  Again, I am lost.  (I come from the subversion world 
> which 
> > seems easy.) 
> 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'. 
> > Also, now that I can see some sort of branches that were created 
> somewhere 
> > else and have some sort of other status, how can I tell where these 
> branches 
> > 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 
> order 
> > 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. 
> -- 
> Felipe Contreras 

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

Reply via email to