Steven Grimm <koreth@xxxxxxxxxxxxx> writes: > Junio C Hamano wrote: >> 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. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
