summaryrefslogtreecommitdiff
path: root/builtin/merge-tree.c
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2022-06-18 00:20:51 (GMT)
committerJunio C Hamano <gitster@pobox.com>2022-06-22 23:10:06 (GMT)
commita4040cfa35d8781df3e994380d1b559be8b22bd2 (patch)
treed6b8ebcb556a2311f185ee2c8878eaeea59baf17 /builtin/merge-tree.c
parentfae26ce79cad6d290e296e40f2d46eb783e91110 (diff)
downloadgit-a4040cfa35d8781df3e994380d1b559be8b22bd2.zip
git-a4040cfa35d8781df3e994380d1b559be8b22bd2.tar.gz
git-a4040cfa35d8781df3e994380d1b559be8b22bd2.tar.bz2
merge-ort: remove command-line-centric submodule message from merge-ort
There was one case in merge-ort that would call path_msg() multiple times for the same logical conflict, and it was in order to give advice about how to resolve a conflict. This advice does not make as much sense with remerge-diff, or with merge-tree being invoked by a GitHub GUI for resolution of messages, and is making it hard to provide which-logical-conflict-affects-which-paths information in a machine parseable way to a higher level caller of merge-tree. Let's simply remove this informational message. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/merge-tree.c')
0 files changed, 0 insertions, 0 deletions