Re: thoughts on setting core.logAllRefUpdates default true for bare repos

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Nov 5, 2009, 01:28 UTC
Message-ID: <2e24e5b90911041728t72fe2c2fhbea5b8e707236fa@mail.gmail.com>
In-Reply-To: <7v3a4ugjea.fsf@alter.siamese.dyndns.org>

On Thu, Nov 5, 2009 at 1:19 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> The single most common reason why a bare repository is bare is because
> nobody regularly logs in to the machine that hosts it and goes there to
> access its contents.  As reflog is a local thing, and not exposed to
> outside world, enabling it alone would not help a lot to people who do not
> have such a direct access to the bare repository, which by definition is
> the majority because the reason why the repository is bare to begin with.
>
> Once we add ways to expose information kept in reflog of a bare repository
> more effectively and conveniently, the argument could become "should be
> enabled now it would be very useful to have one".

It doesn't have to be exposed nor we have to wait till such features (like you mentioned gitweb, remote log, etc) are implemented.

We're talking "disaster recovery", not "daily use" -- after all, *someone* has access to the machine, and can become "local" to it.

Regards,

Sitaram