Re: [PATCH] push: Enhance unspecified push default warning
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Oct 3, 2013, 06:48 UTC
- Message-ID
- <vpqr4c2kfyh.fsf@anie.imag.fr>
- In-Reply-To
- <CAKYC+eLGS6ocdE7CTV25E2xMRaHijmQbFBc3tAyx3cNpXfC_sg@mail.gmail.com>
Coder Coder5000 <coder5000@gmail.com> writes: ^^^^^^^^^^^^^^^ Please, use your real identity in your From: field (git send-email may help).
Show 16 quoted lines
> --- a/builtin/push.c
> +++ b/builtin/push.c
> @@ -174,6 +174,15 @@ N_("push.default is unset; its implicit value is
> changing in\n"
> "\n"
> " git config --global push.default simple\n"
> "\n"
> + "When push.default is set to matching git will push all local branches\n"
> + "to the remote branches with the same (matching) name. This will no\n"
> + "longer be the default in Git 2.0 because a branch could be\n"
> + "unintentionally pushed to a remote.\n"
> + "\n"
> + "In Git 2.0 the new push.default of simple will push only the current\n"
> + "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"
> + "\n"It is becoming a monster-warning, but I think this is a good change. People who still see the warning are those who did not upgrade for a while (and therefore probably the ones needing the most explanation). And it's meant to be a one-time warning anyway.
Judging by the question asked on stackoverflow ( http://stackoverflow.com/questions/13148066/warning-push-default-is-unset-its-implicit-value-is-changing-in-git-2-0 ) and its popularity, telling the users to read the docs did not work very well.
Thanks,
-- Matthieu Moy http://www-verimag.imag.fr/~moy/