| commit | 751c59746c7522982214528eb653dfb61d372257 | |
| author | Jeff King <peff@peff.net> | |
| Sun, 9 Aug 2009 10:02:24 +0000 (9 06:02 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 9 Aug 2009 19:34:20 +0000 (9 12:34 -0700) | ||
| tree | 7be0dd989eaef7dc37804527402533050ba72491 | treesnapshot (tar.gz zip) |
| parent | ce0646184696ae6d87c0e243d058cf5df6459c4f | commitdiff |
merge: fix incorrect merge message for ambiguous tag/branch
If we have both a tag and a branch named "foo", then calling
"git merge foo" will warn about the ambiguous ref, but merge
the tag.
When generating the commit message, though, we simply
checked whether "refs/heads/foo" existed, and if it did,
assumed it was a branch. This led to the statement "Merge
branch 'foo'" in the commit message, which is quite wrong.
Instead, we should use dwim_ref to find the actual ref used,
and describe it appropriately.
In addition to the test in t7608, we must also tweak the
expected output of t4202, which was accidentally triggering
this bug.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If we have both a tag and a branch named "foo", then calling
"git merge foo" will warn about the ambiguous ref, but merge
the tag.
When generating the commit message, though, we simply
checked whether "refs/heads/foo" existed, and if it did,
assumed it was a branch. This led to the statement "Merge
branch 'foo'" in the commit message, which is quite wrong.
Instead, we should use dwim_ref to find the actual ref used,
and describe it appropriately.
In addition to the test in t7608, we must also tweak the
expected output of t4202, which was accidentally triggering
this bug.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin-merge.c | diffblobblamehistory | |
| t/t4202-log.sh | diffblobblamehistory | |
| t/t7608-merge-messages.sh | diffblobblamehistory |