Steffen Prohaska <prohaska@xxxxxx> writes: > What's left is a new switch "--current". Less code, easy > to explain. But won't that force the "current" people always type that from the command line, as your previous point was that your earlier patch to say "remote.$there.push = HEAD" does not work that way? If that configuration works as expected, then I'd 100% agree that we would not need push.defaultRefs. Either you do not have "push" at all if your preference is --matching, or you do have "push = HEAD" if your preference is --current. But if it doesn't (which was what I gathered from your earlier response), having a configuration would help them, wouldn't it? Changing the default, if it will ever happen, is _NOT_ to help people who are already using git and want "current" NOW. The current users cannot be helped _unless_ we switch overnight, but that is not an option as it introduces a regression to people's established workflow. Changing the default is to help new users who will come in the future, if majority of the existing users find --current easier to explain to new people _they_ need to train. - 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
