Junio C Hamano <gitster@xxxxxxxxx> writes:
> Telling somebody who would blindly follow what was suggested to use
> 'current' is what bothers me.
That is (quoting the difference between the previous round and this
one),
static char warn_unspecified_push_default_msg[] =
N_("push.default is unset; its implicit value is changing in\n"
"Git 2.0 from 'matching' to 'simple'. To squelch this message\n"
"and maintain the current behavior after the default changes, use:\n"
"\n"
" git config --global push.default matching\n"
"\n"
"To squelch this message and adopt the new behavior now, use:\n"
"\n"
" git config --global push.default simple\n"
"\n"
- "See 'git help config' and search for 'push.default' for further information.");
+ "See 'git help config' and search for 'push.default' for further information.\n"
+ "(the 'simple' mode was introduced in Git 1.7.11. Use 'current' instead if\n"
+ "you sometimes use older versions of Git)");
The latter half of the message is "To *adopt* the *new behaviour
now*" but setting it to 'current' is not adopting the new behaviour.
Perhaps we should say more to help people decide which one to choose
in this message.
... changing in Git 2.0 from 'matching' to 'simple'.
'matching', which is the current default, pushes all branches
that exist at the remote. 'simple', which will be the new
default, pushes only the current branch to update the branch at
the remote of the same name (the 'simple' mode is only available
in Git 1.7.11 or newer; older versions of Git has a similar mode
called 'current').
You can squelch this message by picking your preferred default now,
e.g. running one of these:
git config push.default matching
git config push.default simple
git config push.default current
or something?
--
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