From: demerphq <demerphq@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: thoughts on setting core.logAllRefUpdates default true for bare repos
Date: Wed, 4 Nov 2009 18:15:17 +0100 [thread overview]
Message-ID: <9b18b3110911040915q1dfa5a4bk18087d93a00f4cf5@mail.gmail.com> (raw)
In-Reply-To: <2e24e5b90911040841l7741787et48fabb8c8066e946@mail.gmail.com>
2009/11/4 Sitaram Chamarty <sitaramc@gmail.com>:
> 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.
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/"
next prev parent reply other threads:[~2009-11-04 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 12:55 thoughts on setting core.logAllRefUpdates default true for bare repos Sitaram Chamarty
2009-11-04 13:25 ` Johannes Schindelin
2009-11-04 16:41 ` Sitaram Chamarty
2009-11-04 17:15 ` demerphq [this message]
2009-11-04 23:52 ` Nicolas Sebrecht
2009-11-04 23:59 ` Sverre Rabbelier
2009-11-05 1:24 ` Sitaram Chamarty
2009-11-04 19:35 ` Matthieu Moy
2009-11-04 19:49 ` Junio C Hamano
2009-11-04 20:42 ` Matthieu Moy
2009-11-05 1:28 ` Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9b18b3110911040915q1dfa5a4bk18087d93a00f4cf5@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).