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

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Nov 4, 2009, 16:41 UTC
Message-ID: <2e24e5b90911040841l7741787et48fabb8c8066e946@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0911041422170.2788@felix-maschine>

Hi Johannes,

On Wed, Nov 4, 2009 at 6:55 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> I did not have time yet to investigate, but it seems that there are
> problems with the permissions of shared bare repositories when activating
> the reflogs.

Interesting; I will try and investigate if I can find something.

> With gitweb on a public site, there might be a problem when you pushed
> some blob containing trade secrets accidentally, and try to scrub the
> repository using "git gc" after a forced push.

Agreed. This config variable is biased to *keep* data if set to true, and (default) false value is biased not to keep that same data, so that will always be a conflict.

But if you are able to do "gc" manually on any repo you can also do "reflog expire" before "gc" can you not? Please correct me if I'm wrong.

Regards,

Sitaram