merge-ort: optionally produce machine-readable output
commitde90581141a886a79cccd0d9adb76814f3e1ab2c
authorElijah Newren <newren@gmail.com>
Sat, 18 Jun 2022 00:20:57 +0000 (18 00:20 +0000)
committerJunio C Hamano <gitster@pobox.com>
Wed, 22 Jun 2022 23:10:06 +0000 (22 16:10 -0700)
tree78f5313b9c5c1bd2afb3da9c1a334e54059b6dea
parentcb2607759e27627aca614726dc50e98ac0ba6d19
merge-ort: optionally produce machine-readable output

With the new `detailed` parameter, a new mode can be triggered when
displaying the merge messages: The `detailed` mode prints NUL-delimited
fields of the following form:

<path-count> NUL <path>... NUL <conflict-type> NUL <message>

The `<path-count>` field determines how many `<path>` fields there are.

The intention of this mode is to support server-side operations, where
worktree-less merges can lead to conflicts and depending on the type
and/or path count, the caller might know how to handle said conflict.

Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/merge-tree.c
merge-ort.c
merge-ort.h