From: Sitaram Chamarty <sitaramc@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: thoughts on setting core.logAllRefUpdates default true for bare repos
Date: Wed, 4 Nov 2009 22:11:11 +0530 [thread overview]
Message-ID: <2e24e5b90911040841l7741787et48fabb8c8066e946@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2009-11-04 16:41 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 [this message]
2009-11-04 17:15 ` demerphq
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=2e24e5b90911040841l7741787et48fabb8c8066e946@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).