summaryrefslogtreecommitdiff
path: root/t/t5515/refs.br-remote-glob
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2008-04-16 12:50:48 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2008-04-16 12:50:48 -0700
commit5e835cac8622373724235d299f1331ac4cf81ccf (patch)
tree9fc04991e376b8d4152ba39b8f268cc6d8c1188e /t/t5515/refs.br-remote-glob
parentMerge branch 'maint-1.5.4' into maint (diff)
downloadtgif-5e835cac8622373724235d299f1331ac4cf81ccf.tar.xz
rebase: do not munge commit log message
Traditionally git-rebase was implemented in terms of "format-patch" piped to "am -3", to strike balance between speed (because it avoids a rather expensive read-tree/merge-recursive machinery most of the time) and flexibility (the magic "-3" allows it to fall back to 3-way merge as necessary). However, this combination has one flaw when dealing with a nonstandard commit log message format that has more than one lines in the first paragraph. This teaches "git am --rebasing" to take advantage of the fact that the mbox message "git rebase" prepares for it records the original commit object name, to get the log message from the original commit object instead. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/refs.br-remote-glob')
0 files changed, 0 insertions, 0 deletions