From 5d1f5b8cd4bec8fbb405e32b1208955c93240f17 Mon Sep 17 00:00:00 2001 From: Jeff King Date: Fri, 24 Sep 2021 14:46:37 -0400 Subject: repack, prune: drop GIT_REF_PARANOIA settings Now that GIT_REF_PARANOIA is the default, we don't need to selectively enable it for destructive operations. In fact, it's harmful to do so, because it overrides any GIT_REF_PARANOIA=0 setting that the user may have provided (because they're trying to work around some corruption). With these uses gone, we can further clean up the ref_paranoia global, and make it a static variable inside the refs code. Signed-off-by: Jeff King Reviewed-by: Jonathan Tan Signed-off-by: Junio C Hamano --- cache.h | 8 -------- 1 file changed, 8 deletions(-) (limited to 'cache.h') diff --git a/cache.h b/cache.h index f6295f3b04..f445008895 100644 --- a/cache.h +++ b/cache.h @@ -994,14 +994,6 @@ extern const char *core_fsmonitor; extern int core_apply_sparse_checkout; extern int core_sparse_checkout_cone; -/* - * Include broken refs in all ref iterations, which will - * generally choke dangerous operations rather than letting - * them silently proceed without taking the broken ref into - * account. - */ -extern int ref_paranoia; - /* * Returns the boolean value of $GIT_OPTIONAL_LOCKS (or the default value). */ -- cgit v1.3