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>
Jeff King committed
Jul 18, 2018 at 16:44 UTC
72470aa38ad786697118157e69174ba7ff85bfa3
1 file changed
+1
-3
cache.h
+1
-3
@@ -804,9 +804,7 @@ void reset_shared_repository(void);
804
* Do replace refs need to be checked this run? This variable is
805
* initialized to true unless --no-replace-object is used or
806
* $GIT_NO_REPLACE_OBJECTS is set, but is set to false by some
807
- * commands that do not want replace references to be active. As an
808
- * optimization it is also set to false if replace references have
809
- * been sought but there were none.
807
+ * commands that do not want replace references to be active.
808
*/
809
extern int check_replace_refs;
810
extern char *git_replace_ref_base;