summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2018-07-18 16:44:49 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-07-18 15:45:06 -0700
commit72470aa38ad786697118157e69174ba7ff85bfa3 (patch)
tree4f8482b0b07b75434a61f6ca93f4dd313aad92c4
parentThird batch for 2.19 cycle (diff)
downloadtgif-72470aa38ad786697118157e69174ba7ff85bfa3.tar.xz
check_replace_refs: fix outdated comment
Commit afc711b8e1 (rename read_replace_refs to check_replace_refs, 2014-02-18) added a comment mentioning that check_replace_refs is set in two ways: - from user intent via --no-replace-objects, etc - after seeing there are no replace refs to respect Since c3c36d7de2 (replace-object: check_replace_refs is safe in multi repo environment, 2018-04-11) the second is no longer true. Let's drop that part of the comment. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--cache.h4
1 files changed, 1 insertions, 3 deletions
diff --git a/cache.h b/cache.h
index 8b447652a7..7b09b09cb0 100644
--- a/cache.h
+++ b/cache.h
@@ -804,9 +804,7 @@ void reset_shared_repository(void);
* Do replace refs need to be checked this run? This variable is
* initialized to true unless --no-replace-object is used or
* $GIT_NO_REPLACE_OBJECTS is set, but is set to false by some
- * commands that do not want replace references to be active. As an
- * optimization it is also set to false if replace references have
- * been sought but there were none.
+ * commands that do not want replace references to be active.
*/
extern int check_replace_refs;
extern char *git_replace_ref_base;