merge: make debug output easier to read
I always found it hard to figure out what the debug code meant without the separators.
Showing
- mercurial/merge.py 3 additions, 2 deletionsmercurial/merge.py
- tests/test-copy-move-merge.t 2 additions, 2 deletionstests/test-copy-move-merge.t
- tests/test-double-merge.t 2 additions, 2 deletionstests/test-double-merge.t
- tests/test-graft.t 6 additions, 6 deletionstests/test-graft.t
- tests/test-issue1802.t 2 additions, 2 deletionstests/test-issue1802.t
- tests/test-issue522.t 2 additions, 2 deletionstests/test-issue522.t
- tests/test-issue672.t 6 additions, 6 deletionstests/test-issue672.t
- tests/test-merge-commit.t 4 additions, 4 deletionstests/test-merge-commit.t
- tests/test-merge-types.t 4 additions, 4 deletionstests/test-merge-types.t
- tests/test-merge7.t 2 additions, 2 deletionstests/test-merge7.t
- tests/test-rename-dir-merge.t 4 additions, 4 deletionstests/test-rename-dir-merge.t
- tests/test-rename-merge1.t 2 additions, 2 deletionstests/test-rename-merge1.t
- tests/test-rename-merge2.t 42 additions, 42 deletionstests/test-rename-merge2.t
- tests/test-subrepo.t 8 additions, 8 deletionstests/test-subrepo.t
- tests/test-up-local-change.t 8 additions, 8 deletionstests/test-up-local-change.t
- tests/test-update-reverse.t 2 additions, 2 deletionstests/test-update-reverse.t
Loading
Please register or sign in to comment