Commit eec7f53
diff --color-moved: stop clearing potential moved blocks
moved_block_clear() was introduced in 74d156f ("diff
--color-moved-ws: fix double free crash", 2018-10-04) to free the
memory that was allocated when initializing a potential moved
block. However since 21536d0 ("diff --color-moved-ws: modify
allow-indentation-change", 2018-11-23) initializing a potential moved
block no longer allocates any memory. Up until the last commit we were
relying on moved_block_clear() to set the `match` pointer to NULL when
a block stopped matching, but since that commit we do not clear a
moved block that does not match so it does not make sense to clear
them elsewhere.
Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
Signed-off-by: Junio C Hamano <gitster@pobox.com>1 parent 0e488f1 commit eec7f53
1 file changed
+0
-11
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
807 | 807 | | |
808 | 808 | | |
809 | 809 | | |
810 | | - | |
811 | | - | |
812 | | - | |
813 | | - | |
814 | | - | |
815 | 810 | | |
816 | 811 | | |
817 | 812 | | |
| |||
1128 | 1123 | | |
1129 | 1124 | | |
1130 | 1125 | | |
1131 | | - | |
1132 | | - | |
1133 | 1126 | | |
1134 | 1127 | | |
1135 | 1128 | | |
| |||
1139 | 1132 | | |
1140 | 1133 | | |
1141 | 1134 | | |
1142 | | - | |
1143 | | - | |
1144 | 1135 | | |
1145 | 1136 | | |
1146 | 1137 | | |
| |||
1193 | 1184 | | |
1194 | 1185 | | |
1195 | 1186 | | |
1196 | | - | |
1197 | | - | |
1198 | 1187 | | |
1199 | 1188 | | |
1200 | 1189 | | |
| |||
0 commit comments