path: root/t/
diff options
authorJeff King <>2018-07-18 20:45:25 (GMT)
committerJunio C Hamano <>2018-07-18 22:45:27 (GMT)
commitda4398d6a03eb2cf857aa63190e9bf60305befd2 (patch)
tree61335160817ac56d4c0ad7014b8b4d0670435e95 /t/
parent6ebd1cafe2bb1dee34e106a8da3ee173b36259d3 (diff)
add core.usereplacerefs config option
We can already disable replace refs using a command line option or environment variable, but those are awkward to apply universally. Let's add a config option to do the same thing. That raises the question of why one might want to do so universally. The answer is that replace refs violate the immutability of objects. For instance, if you wanted to cache the diff between commit XYZ and its parent, then in theory that never changes; the hash XYZ represents the total state. But replace refs violate that; pushing up a new ref may create a completely new diff. The obvious "if it hurts, don't do it" answer is not to create replace refs if you're doing this kind of caching. But for a site hosting arbitrary repositories, they may want to allow users to share replace refs with each other, but not actually respect them on the site (because the caching is more important than the replace feature). Signed-off-by: Jeff King <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 't/')
1 files changed, 6 insertions, 0 deletions
diff --git a/t/ b/t/
index aa3e249..86374a9 100755
--- a/t/
+++ b/t/
@@ -113,6 +113,12 @@ test_expect_success 'test GIT_NO_REPLACE_OBJECTS env variable' '
GIT_NO_REPLACE_OBJECTS=1 git show $HASH2 | grep "A U Thor"
+test_expect_success 'test core.usereplacerefs config option' '
+ test_config core.usereplacerefs false &&
+ git cat-file commit $HASH2 | grep "author A U Thor" &&
+ git show $HASH2 | grep "A U Thor"
cat >tag.sig <<EOF
object $HASH2
type commit