On Mon, Nov 03, 2008 at 11:33:10PM +0000, Junio C Hamano wrote: > Pierre Habouzit <madcoder@xxxxxxxxxx> writes: > > > On Sun, Nov 02, 2008 at 10:27:57PM +0000, Junio C Hamano wrote: > >> Jeff King <peff@xxxxxxxx> 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. You're right. > 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? I don't know, I thought git push --matching $remote would be the same as git push $remote ? -- ·O· Pierre Habouzit ··O madcoder@xxxxxxxxxx OOO http://www.madism.org
Attachment:
pgpXfmHHwubU8.pgp
Description: PGP signature
