From: Jeff King Date: Sat, 13 Feb 2010 11:58:34 GMT Subject: Re: Separate default push/pull? Message-ID: <20100213115834.GA7385@coredump.intra.peff.net> In-Reply-To: <7vvde3dmhp.fsf@alter.siamese.dyndns.org> On Thu, Feb 11, 2010 at 09:57:54PM -0800, Junio C Hamano wrote: > Jeff King writes: > > > In a distributed setup, I don't think it is that uncommon to not want to > > push to the place you pull from. You are generally pulling and building > > on somebody else's work, so if there is no central repo, you will be > > pushing to somewhere that is not where you pulled it. > > You are probably right. > > It still feels funny to see "git pull" and "git push" goes to different > places, but as long as that is what the user explicitly configures, that's > fine. By the way, I am a little iffy on the configuration I suggested. Even though it matches David's workflow, it seems unintuitive to me that a "push.defaultremote" variable would override what's in "branch.*.remote". -Peff