author | Junio C Hamano <gitster@pobox.com> | |
Tue, 11 Nov 2008 00:15:49 +0000 (16:15 -0800) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Fri, 23 Jul 2010 21:46:28 +0000 (14:46 -0700) | ||
commit | 840b3ca758a42cb1481259521126ba2b02a5447a | |
tree | 127238c896ab3dcf9bed7eb4a360f02032f5f1a1 | tree | snapshot |
parent | e877a4c11a947789a8b88234e458164ea16675bd | commit | diff |
rebase: protect against diff.renames configuration
We currently do not disable diff.renames configuration while rebase
internally runs "format-patch" to feed "am -3".
The end user configuration for "diff" should not affect the result
produced by the higher level command that is related to "diff" only
because internally it is implemented in terms of it.
For that matter, I have a feeling that format-patch should not even look
at diff.renames, but we seem to have been doing this for a long time so
there is no easy way to fix this thinko.
In any case, here is a much straightforward fix for "rebase".
[jn: with test case from David]
Reported-by: David D. Kilzer <ddkilzer@kilzer.net>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
We currently do not disable diff.renames configuration while rebase
internally runs "format-patch" to feed "am -3".
The end user configuration for "diff" should not affect the result
produced by the higher level command that is related to "diff" only
because internally it is implemented in terms of it.
For that matter, I have a feeling that format-patch should not even look
at diff.renames, but we seem to have been doing this for a long time so
there is no easy way to fix this thinko.
In any case, here is a much straightforward fix for "rebase".
[jn: with test case from David]
Reported-by: David D. Kilzer <ddkilzer@kilzer.net>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
git-rebase.sh | diff | blob | history | |
t/t3400-rebase.sh | diff | blob | history |