[PATCH 02/12] rerere: convert flags into an enum
- From
Patrick Steinhardt <ps@pks.im>
- Date
- Oct 27, 2026, 10:46 UTC
- Message-ID
- <20261027-pks-rerere-subcommands-v1-2-d836c36ce0c5@pks.im>
- In-Reply-To
- <20261027-pks-rerere-subcommands-v1-0-d836c36ce0c5@pks.im>
Our modern coding guidelines say that flags should typically be passed around as enums so that it becomes trivial to see what kind of flags are expected. Adapt the rerere flags accordingly.
Signed-off-by: Patrick Steinhardt <ps@pks.im> --- rerere.c | 7 ++++--- rerere.h | 21 ++++++++++++--------- 2 files changed, 16 insertions(+), 12 deletions(-)
diff --git a/rerere.c b/rerere.c index fd1c1ed6015..1ae7983445a 100644 --- a/rerere.c +++ b/rerere.c @@ -908,7 +908,7 @@ static int is_rerere_enabled(struct repository *r) int rerere_cache_setup(struct rerere_cache *cache, struct repository *r, struct string_list *merge_rr, - int flags) + enum rerere_flags flags) { int lock_timeout_ms = 1000; int fd; @@ -956,7 +956,7 @@ int rerere_cache_setup(struct rerere_cache *cache, * perform mergy operations, possibly leaving conflicted index entries * and working tree files. */ -int rerere_record(struct repository *r, int flags) +int rerere_record(struct repository *r, enum rerere_flags flags) { struct string_list merge_rr = STRING_LIST_INIT_DUP; struct rerere_cache cache; @@ -1341,7 +1341,8 @@ bool rerere_gc_needed(struct repository *r, size_t limit) return needed; } -void rerere_gc(struct repository *r, struct string_list *rr, int flags) +void rerere_gc(struct repository *r, struct string_list *rr, + enum rerere_flags flags) { struct rerere_cache cache; struct string_list to_remove = STRING_LIST_INIT_DUP; diff --git a/rerere.h b/rerere.h index a19d2407b59..362b348af25 100644 --- a/rerere.h +++ b/rerere.h @@ -9,12 +9,6 @@ struct pathspec; struct repository; -#define RERERE_AUTOUPDATE 01 -#define RERERE_NOAUTOUPDATE 02 -#define RERERE_READONLY 04 -/* If MERGE_RR.lock is taken, return -1 as if rerere were disabled */ -#define RERERE_NOWAIT 010 - /* * Marks paths that have been hand-resolved and added to the * index. Set in the util field of such paths after calling @@ -39,13 +33,21 @@ struct rerere_id { int variant; }; +enum rerere_flags { + RERERE_AUTOUPDATE = (1 << 0), + RERERE_NOAUTOUPDATE = (1 << 1), + RERERE_READONLY = (1 << 2), + /* If MERGE_RR.lock is taken, return -1 as if rerere were disabled */ + RERERE_NOWAIT = (1 << 3), +}; + int rerere_cache_setup(struct rerere_cache *cache, struct repository *r, struct string_list *merge_rr, - int flags); + enum rerere_flags flags); void rerere_cache_release(struct rerere_cache *cache); -int rerere_record(struct repository *, int); +int rerere_record(struct repository *r, enum rerere_flags flags); /* * Given the conflict ID and the name of a "file" used for replaying * the recorded resolution (e.g. "preimage", "postimage"), return the @@ -58,7 +60,8 @@ const char *rerere_path(struct repository *, int rerere_forget(struct repository *, struct pathspec *); int rerere_remaining(struct repository *, struct string_list *); void rerere_clear(struct repository *, struct string_list *); -void rerere_gc(struct repository *, struct string_list *, int); +void rerere_gc(struct repository *, struct string_list *, + enum rerere_flags flags); /* * Check whether garbage collection for rerere entries is needed, which is
-- 2.56.0.341.g393f52fd96.dirty