From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 00/10] push: switch default from "matching" to "simple"
Date: Fri, 4 Jan 2013 22:52:58 -0800 [thread overview]
Message-ID: <1357368788-28035-1-git-send-email-gitster@pobox.com> (raw)
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
next reply other threads:[~2013-01-05 6:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 6:52 Junio C Hamano [this message]
2013-01-05 6:52 ` [PATCH 01/10] t5404: do not assume the "matching" push is the default Junio C Hamano
2013-01-05 6:53 ` [PATCH 02/10] t5505: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 03/10] t5516: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 04/10] t5517: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 05/10] t5519: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 06/10] t5531: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 07/10] t7406: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 08/10] t9400: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 09/10] t9401: " Junio C Hamano
2013-01-05 6:53 ` [PATCH 10/10] push: switch default from "matching" to "simple" Junio C Hamano
2013-01-05 19:39 ` [PATCH 00/10] " Matthieu Moy
2013-01-08 22:28 ` [PATCH 11/10] doc: push.default is no longer "matching" Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1357368788-28035-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).