Re: [RFC/PATCH] enable rerere by default

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 6, 2007, 15:53 UTC
Message-ID: <Pine.LNX.4.63.0702061649520.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <81b0412b0702060739y35c00332q8945a33743084219@mail.gmail.com>

Hi,

On Tue, 6 Feb 2007, Alex Riesen wrote:

Show 16 quoted lines

> On 2/6/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> 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.

Okay, but this is a little involved:

$ grep -l rr-cache *.{c,h,sh,perl} builtin-rerere.c git-am.sh git-commit.sh git-merge.sh git-rebase.sh git-reset.sh

So, unless the list agrees that rerere should be enabled by default, I will not make a patch to move rerere enabling to the config.

Ciao, Dscho