On Monday, May 18, 2015 at 5:58:47 AM UTC-4, Konstantin Khomoutov wrote:
> On Sun, 17 May 2015 17:31:03 -0400 
> wor...@alum.mit.edu <javascript:> (Dale R. Worley) wrote: 
> > John Bleichert <jblei...@gmail.com <javascript:>> writes: 
> <snip>

> Basically, that's what 
>   git remote -v show <remote> 
> does: it reaches for the server behind <remote> asks it for the 
> refs/heads/* it has, compares them to the local heads, including their 
> tracking state, and outputs the results in a human-readable form. 

Thanks for all the replies - I appreciate it. 

Konstantin's advice above seems to do the trick, though I still have some 
reading to do...


$ git remote -v show origin
* remote origin                                                             
  Fetch URL: bitbucket.org...                                               
  Push  URL: bitbucket.org:..
  HEAD branch: master
  Remote branch:
    master tracked
  Local branch configured for 'git pull':
    master merges with remote master
  Local ref configured for 'git push':
    master pushes to master (local out of date)

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 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to