aboutsummaryrefslogtreecommitdiff
path: root/resolve-undo.h
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2024-12-17 07:43:57 +0100
committerJunio C Hamano <gitster@pobox.com>2024-12-18 10:44:31 -0800
commitb81093aeae557d56277773dee710eb363c720b6e (patch)
treeb818e5c776962273c36493e133b88d6030a2a624 /resolve-undo.h
parent6c27d22276b754e2214242de7a200b372aa611f6 (diff)
downloadgit-b81093aeae557d56277773dee710eb363c720b6e.tar.xz
resolve-undo: stop using `the_repository`
Stop using `the_repository` in the "resolve-undo" subsystem by passing in the hash algorithm when reading or writing resolve-undo information. While we could trivially update the caller to pass in the hash algorithm used by the index itself, we instead pass in `the_hash_algo`. This is mostly done to stay consistent with the rest of the code in that file, which isn't prepared to handle arbitrary repositories, either. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'resolve-undo.h')
-rw-r--r--resolve-undo.h6
1 files changed, 4 insertions, 2 deletions
diff --git a/resolve-undo.h b/resolve-undo.h
index 89a3227262..7ed11a1c59 100644
--- a/resolve-undo.h
+++ b/resolve-undo.h
@@ -14,8 +14,10 @@ struct resolve_undo_info {
};
void record_resolve_undo(struct index_state *, struct cache_entry *);
-void resolve_undo_write(struct strbuf *, struct string_list *);
-struct string_list *resolve_undo_read(const char *, unsigned long);
+void resolve_undo_write(struct strbuf *, struct string_list *,
+ const struct git_hash_algo *algop);
+struct string_list *resolve_undo_read(const char *, unsigned long,
+ const struct git_hash_algo *algop);
void resolve_undo_clear_index(struct index_state *);
int unmerge_index_entry(struct index_state *, const char *, struct resolve_undo_info *, unsigned);
void unmerge_index(struct index_state *, const struct pathspec *, unsigned);