author | Vincent van Ravesteijn <vfr@lyx.org> | |
Mon, 21 Nov 2011 13:30:40 +0000 (14:30 +0100) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Mon, 21 Nov 2011 17:29:06 +0000 (09:29 -0800) | ||
commit | 5480207c4ee395fbb82682bc2065c93a43e24328 | |
tree | e207d6959d00b6caf08960f466f2f5a228f39ec9 | tree | snapshot |
parent | bd5bce7cbc55fa52277cc8a39f673c3e2dc60670 | commit | diff |
Show error for 'git merge' with unset merge.defaultToUpstream
'git merge' can be called without any arguments if merge.defaultToUpstream
is set. However, when merge.defaultToUpstream is not set, the user will be
presented the usage information as if he entered a command with a wrong
syntaxis. Ironically, the usage information confirms that no arguments are
mandatory.
This adds a proper error message telling the user why the command failed. As
a side-effect this can help the user in discovering the possibility to merge
with the upstream branch by setting merge.defaultToUpstream.
Signed-off-by: Vincent van Ravesteijn <vfr@lyx.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
'git merge' can be called without any arguments if merge.defaultToUpstream
is set. However, when merge.defaultToUpstream is not set, the user will be
presented the usage information as if he entered a command with a wrong
syntaxis. Ironically, the usage information confirms that no arguments are
mandatory.
This adds a proper error message telling the user why the command failed. As
a side-effect this can help the user in discovering the possibility to merge
with the upstream branch by setting merge.defaultToUpstream.
Signed-off-by: Vincent van Ravesteijn <vfr@lyx.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/merge.c | diff | blob | history |