If a merge tool was invoked on a conflicted file and the tool completed, then the conflicted file was staged automatically. However, the fact that the user closed the merge tool cannot be understood as the unequivocal sign that the conflict was completely resolved. For example, the user could have decided to postpone the resolution of the conflict, or could have accidentally closed the tool. We better leave the file unstaged and let the user stage it explicitly. Signed-off-by: Johannes Sixt --- On Mittwoch, 24. September 2008, Shawn O. Pearce wrote: > Alexander Gavrilov wrote: > > You also cannot simply remove merge_add_resolution, because then it > > would leave the diff view stale. > > Is it just a matter of calling reshow_diff instead? Indeed. I'd tried do_rescan, but reshow_diff does it, too, and it doesn't mess with the file lists! This version of the patch also removes the check whether the merge tool had modified the file, because now we don't do anything with the file anyway. -- Hannes lib/mergetool.tcl | 10 +--------- 1 files changed, 1 insertions(+), 9 deletions(-) diff --git a/lib/mergetool.tcl b/lib/mergetool.tcl index 965cfe4..f292f30 100644 --- a/lib/mergetool.tcl +++ b/lib/mergetool.tcl @@ -348,14 +348,6 @@ proc merge_tool_finish {fd} { } } - # Check the modification time of the target file - if {!$failed && [file mtime $mtool_target] eq $mtool_mtime} { - if {[ask_popup [mc "File %s unchanged, still accept as resolved?" \ - [short_path $mtool_target]]] ne {yes}} { - set failed 1 - } - } - # Finish if {$failed} { file rename -force -- $backup $mtool_target @@ -368,6 +360,6 @@ proc merge_tool_finish {fd} { delete_temp_files $mtool_tmpfiles - merge_add_resolution $mtool_target + reshow_diff } } -- 1.6.0.2.295.g3898d -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html