On Thu, Apr 11, 2013 at 03:36:10AM +0530, Ramkumar Ramachandra wrote: > Jeff King wrote: > > It's not that it's not potentially useful. It's that it may be > > surprising and annoying to users who did not want that. > > ... but this is a new syntax, and doesn't break any existing > expectations. Why are you imagining what users will expect with a git > push -- master next; that hasn't been invented yet?
Didn't I already say that I expected a different behavior than you are proposing from "git push -- v1.2.3 master"? Yes, it is possible to lay out all of the rules in the manpage so that the user can predict what will happen. But users do not always know or remember all of those rules, especially if it "just works" most of the time (e.g., they usually push two branches, but this time push a tag). If a command is easy to screw up, people will screw it up, and get surprised and annoyed when it happens. We can say "well, you should have read the manpage", but it is much nicer if we can come up with a command that is harder to screw up. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
