From: Alex Riesen Date: Tue, 06 Feb 2007 15:39:52 GMT Subject: Re: [RFC/PATCH] enable rerere by default Message-ID: <81b0412b0702060739y35c00332q8945a33743084219@mail.gmail.com> In-Reply-To: On 2/6/07, Johannes Schindelin wrote: > > > I know it is quite late in the game for 1.5.0, but since the theme > > > is usability and user-friendliness, I cannot think of a better > > > release to enable rerere by default, if that should ever happen. > > > > > > Comments? > > > > 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.) I suggest a config variable defaulting to "on", able to disable rerere even if rr-cache exists. So the var has at least theoretical use also after a repo is created. I'll put it in templates config then, and modify existing repos to switch it "off" (so I always have it mentioned in the configs). Newbies, who don't have it own templates, wont even notice it. Unless it is put into the generated config, that is: like core.logallrefupdates - it can be in templates config, or git-init writes it.