Marc Branchaud <marcn...@xiplink.com> writes:
>> - "In Git 2.0 the new push.default of 'simple' will push only the
>> - "branch to the same remote branch used by git pull. A push will\n"
>> - "only succeed if the remote and local branches have the same name.\n"
>> + "In Git 2.0, Git will default to the more conservative 'simple'\n"
>> + "behavior that only pushes the current branch to the corresponding\n"
>> + "remote branch used by 'git pull' to update the current branch from.\n"
> That reads a bit awkwardly. How about:
> In Git 2.0, Git will default to the more conservative 'simple'
> behavior, which only pushes the current branch to the corresponding
> remote branch that 'git pull' uses to update the current branch.
OK, here is the version of Greg's patch (i.e. for versions before
2.0) with the above. The endgame patch for 2.0 would change the
line that begins with "In Git 2.0," to:
Since Git 2.0, Git defaults to the more conservative ...
Is everybody happy with this version?
-- >8 --
From: Greg Jacobson <coder5...@gmail.com>
Date: Fri, 4 Oct 2013 10:20:07 -0400
Subject: [PATCH] push: Enhance unspecified push default warning
When the unset push.default warning message is displayed this may be
the first time many users encounter push.default.
Explain in the warning message in a compact manner what push.default
is and what the change means to the end-user to help the users decide.
Signed-off-by: Greg Jacobson <coder5...@gmail.com>
Helped-by: Jonathan Nieder <jrnie...@gmail.com>
Helped-by: Matthieu Moy <matthieu....@imag.fr>
Helped-by: Marc Branchaud <marcn...@xiplink.com>
Signed-off-by: Junio C Hamano <gits...@pobox.com>
builtin/push.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/builtin/push.c b/builtin/push.c
index 7b1b66c..a73982a 100644
@@ -174,6 +174,13 @@ N_("push.default is unset; its implicit value is changing
" git config --global push.default simple\n"
+ "When push.default is set to 'matching', git will push local branches\n"
+ "to the remote branches that already exist with the same name.\n"
+ "In Git 2.0, Git will default to the more conservative 'simple'\n"
+ "behavior, which only pushes the current branch to the corresponding\n"
+ "remote branch that 'git pull' uses to update the current branch.\n"
"See 'git help config' and search for 'push.default' for further
"(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode\n"
"'current' instead of 'simple' if you sometimes use older versions of
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