Thread (4 messages) flat view 4 messages, 3 authors, 2016-06-15

Re: Git branching & pulling

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:11

Steven Grimm [off-list ref] writes:
Junio C Hamano wrote:
quoted
I personally never understood why people would just want to say
"git pull" without saying anything else, but what described in
the DEFAULT BEHAVIOUR section is how it works.
I do that all the time, e.g. when I'm syncing the satellite repo on my
laptop with the mothership repo in my account on my company's
server. The satellite only ever talks to the mothership and I am
always interested in pulling down all the changes I've committed to
the mothership during the day. So there's really no need to specify
anything; I always want to keep the two fully in sync, and there's
never any question about where I'm pulling from.

I do a plain "git pull" in my clone of git.git too. I want all the
latest updates and I'm only ever fetching them from the official git
repo.
Ah, if you ever interact with only single remote repository,
then that is certainly a valid reason not to say anything else.

And if you ever interact with only single branch of a single
remote repository while on one branch, the current config scheme
would let you do that on any branch.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help