Junio C Hamano <gitster@xxxxxxxxx> writes:
> The manual page for "rerere" talks about "configuration variable
> rerere.enabled"; perhaps it should also refer to git config manual page to
> make it more discoverable?
Maybe, but it already says you should set the variable in two different
places.
> Thomas Rast <trast@xxxxxxxxxxxxxxx> writes:
>
>> ... OTOH the
>> auto-creation of rr-cache can cause strange behavior if a user has
>> rerere.enabled unset and tries it once, as in
>>
>> git config rerere.enabled true
>> git merge ...
>> git config --unset rerere.enabled
>
> That is because the last one should be
>
> git config --bool rerere.enabled false
I definitely meant --unset. If the user knows the distinction, and
wants to return the variable to the state it had before his test
(perhaps so that a future --global setting might take effect), he would
use this sequence. He might then be somewhat surprised to see that
rerere is now permamently enabled for this repo.
Probably I'm worrying too much about a weird fringe case though.
--
Thomas Rast
trast@{inf,student}.ethz.ch
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html