From d366f8e302ddadf9ad6ee74ca5430dcc52a7c67b Mon Sep 17 00:00:00 2001 From: John Estabrook Date: Sun, 16 Mar 2025 22:31:02 -0500 Subject: T7121: keep track of source of subtree from delete or add trees For partial commits with a config error on a subtree, one needs to know the origin of the failed subtree, whether from deletion or addition, in order to contruct the partial successful result. --- src/commit.mli | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'src/commit.mli') diff --git a/src/commit.mli b/src/commit.mli index e765f48..da97389 100644 --- a/src/commit.mli +++ b/src/commit.mli @@ -1,3 +1,5 @@ +type tree_source = DELETE | ADD + type status = { success : bool; out : string; @@ -9,8 +11,9 @@ type node_data = { tag_value: string option; arg_value: string option; path: string list; + source: tree_source; reply: status option; -} [@@deriving yojson] +} [@@deriving to_yojson] type commit_data = { session_id: string; @@ -21,7 +24,7 @@ type commit_data = { background: bool; init: status option; node_list: node_data list; -} [@@deriving yojson] +} [@@deriving to_yojson] val default_node_data : node_data -- cgit v1.2.3