2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:52
Johannes Schindelin [off-list ref] writes:
quoted
How do I disable rerere by default?How'd you like it? Should this rather become a config variable, or do you want to make a file called "rr-cache" in the templates, which just contains a word "disabled"? (git-rerere checks if a _directory_ $GIT_DIR/rr-cache exists.)
Is it so bad to do "rm -rf .git/rr-cache"?
From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:42:52
Hi, On Tue, 6 Feb 2007, Junio C Hamano wrote:
Johannes Schindelin [off-list ref] writes:quoted
quoted
How do I disable rerere by default?How'd you like it? Should this rather become a config variable, or do you want to make a file called "rr-cache" in the templates, which just contains a word "disabled"? (git-rerere checks if a _directory_ $GIT_DIR/rr-cache exists.)Is it so bad to do "rm -rf .git/rr-cache"?
I guess the problem is that you cannot do that by a hook, or by installing appropriate templates. Since the test for rr-cache always is a test for a directory, it might make sense to _not_ fail in init-db when creating the directory. In that case, rerere can be disabled by installing templates which make rr-cache a _file_. Ciao, Dscho