From: Junio C Hamano Date: Mon, 03 Nov 2008 23:33:10 GMT Subject: Re: [PATCH] Documentation: add a planning document for the next CLI revamp Message-ID: <7v4p2ov0zt.fsf@gitster.siamese.dyndns.org> In-Reply-To: <20081103092507.GD13930@artemis.corp> Pierre Habouzit writes: > On Sun, Nov 02, 2008 at 10:27:57PM +0000, Junio C Hamano wrote: >> Jeff King writes: >> >> >> + * 'git push --matching' does what 'git push' does today (without >> >> + explicit configuration) >> > >> > I think this is reasonable even without other changes, just to override >> > any configuration. >> >> I don't. Can't you say "git push $there HEAD" these days? I vaguely >> recall that there is a way to configure push that way for people too lazy >> to type "origin HEAD" after "git push". > > Yes, but it's broken in the sense that if you're in a non matching > branch it creates it remotely. Ok, I agree that may be a problem. But that would not change if you only changed the default behaviour from matching to _this branch_. You need to also teach a new mode of operation to send-pack/receive-pack pair, which is to "update the same branch as the one I am on locally, but do not do anything if there is no such branch over there". I do not think we have such a mode of operation currently. By the way, didn't we add a feature to let you say "git push $there :" which is to do what "git push --matching $there" would do?