Sam Vilain wrote: > On Sun, 2008-11-02 at 14:27 -0800, 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". > > I don't think it's about laziness, it's more about making sure that > without specifying behaviour, the action of the command is conservative. > Pushing all matching refs is not conservative; it's "magic". And in my > experience, people get bitten by it, because they think, "ok, time to > push this branch", type "git push" and then a lot more than they > expected gets pushed. > > I can see that some people want this behaviour by default; but to me > "push the current branch back to where it came from" seems like far more > a rational default for at least 90% of users. "git remote <remote> push" for push matching? -- Jakub Narebski Warsaw, Poland ShadeHawk on #git -- 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
