author | Jeff King <peff@peff.net> | |
Sun, 9 Aug 2009 10:02:51 +0000 (06:02 -0400) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Sun, 9 Aug 2009 19:34:21 +0000 (12:34 -0700) | ||
commit | 69a8b7c74192dfa7bde3937d2c84324a2cd1506b | |
tree | 708d61212040df83649eb7095a88a201cac31af3 | tree | snapshot |
parent | 751c59746c7522982214528eb653dfb61d372257 | commit | diff |
merge: indicate remote tracking branches in merge message
Previously when merging directly from a local tracking
branch like:
git merge origin/master
The merge message said:
Merge commit 'origin/master'
* commit 'origin/master':
...
Instead, let's be more explicit about what we are merging:
Merge remote branch 'origin/master'
* origin/master:
...
We accomplish this by recognizing remote tracking branches
in git-merge when we build the simulated FETCH_HEAD output
that we feed to fmt-merge-msg.
In addition to a new test in t7608, we have to tweak the
expected output of t3409, which does such a merge.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Previously when merging directly from a local tracking
branch like:
git merge origin/master
The merge message said:
Merge commit 'origin/master'
* commit 'origin/master':
...
Instead, let's be more explicit about what we are merging:
Merge remote branch 'origin/master'
* origin/master:
...
We accomplish this by recognizing remote tracking branches
in git-merge when we build the simulated FETCH_HEAD output
that we feed to fmt-merge-msg.
In addition to a new test in t7608, we have to tweak the
expected output of t3409, which does such a merge.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin-merge.c | diff | blob | history | |
t/t3409-rebase-preserve-merges.sh | diff | blob | history | |
t/t7608-merge-messages.sh | diff | blob | history |