We promised to change the behaviour of lazy "git push [there]" that does not say what to push on the command line from "matching" to "simple" in Git 2.0. Even though the top-level RelNotes symbolic link points at 1.8.2, we can change our mind to tag 2.0 at the end of this cycle. This carries out the threat ;-) Mmany tests have assumed that the long established default will never change and relied on the convenience of the "matching" behaviour. They need to be updated to either specify what they want from the command line explicitly, or configure the default behaviour they would expect. And then finally we can flip the default. Junio C Hamano (10): t5404: do not assume the "matching" push is the default t5505: do not assume the "matching" push is the default t5516: do not assume the "matching" push is the default t5517: do not assume the "matching" push is the default t5519: do not assume the "matching" push is the default t5531: do not assume the "matching" push is the default t7406: do not assume the "matching" push is the default t9400: do not assume the "matching" push is the default t9401: do not assume the "matching" push is the default push: switch default from "matching" to "simple" Documentation/config.txt | 6 +++--- builtin/push.c | 31 +++++++------------------------ t/t5404-tracking-branches.sh | 2 +- t/t5505-remote.sh | 2 +- t/t5516-fetch-push.sh | 10 +++++----- t/t5517-push-mirror.sh | 2 +- t/t5519-push-alternates.sh | 12 ++++++------ t/t5531-deep-submodule-push.sh | 1 + t/t7406-submodule-update.sh | 4 ++-- t/t9400-git-cvsserver-server.sh | 1 + t/t9401-git-cvsserver-crlf.sh | 1 + 11 files changed, 29 insertions(+), 43 deletions(-) -- 1.8.1.299.gc73b41f -- 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