Hi, On Sat, 9 Feb 2008, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > > The way would be like this, I think: > > > > - introduce a command line option for push, like "--push-common-refs", > > and issue a warning whenever "git push" is called without command line > > options (along the lines "This default behaviour is deprecated; please > > use --push-common-refs"). > > > > - in a waaaay later version, just take away the default action of "git > > push", instead showing the usage. > > I do not think that is a right approach. To please both camps without > forcing people to > > (1) change what they are used to, and > (2) type overlong command line, > > I think the traditional "matching refs by default", combined with "'git > push HEAD' defaults to pushing the current branch to the default > location" would be a well balanced compromise. I'm no longer that sure. It seems that quite a lot of people do not read manuals, and have no clue what they are doing when they just try $ git push to see what the synopsis is. If there are enough of those people out there, we might want to change our default action to "-h". Yes, that hurts old-timers. Yes, it's not a perfect world. No, I don't want to bend over for just a few people. Ciao, Dscho - 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
