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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2009/11/4 Sitaram Chamarty <sitaramc@xxxxxxxxx>:
> Hi Johannes,
>
> On Wed, Nov 4, 2009 at 6:55 PM, Johannes Schindelin
> <Johannes.Schindelin@xxxxxx> 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.

Assuming you mean via ssh access then if there is we haven't noticed
the problems at $work, and we have had this setup from the first time
somebody did a forced push and broke things, which was like day 3 or
something of our switchover to git from cvs, which is about two years
ago.

IMO it would be nice if the reflog could be set to ONLY record forced
updates. This would make a lot of sense on a bare repo.

Yves

-- 
perl -Mre=debug -e "/just|another|perl|hacker/"
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]