From: Jeff King <peff@peff.net>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Error: unable to unlink ... when using "git gc"
Date: Wed, 7 Jan 2009 00:59:47 -0500 [thread overview]
Message-ID: <20090107055947.GA22616@coredump.intra.peff.net> (raw)
In-Reply-To: <slrngm6uf5.vuo.sitaramc@sitaramc.homelinux.net>
On Tue, Jan 06, 2009 at 03:33:57PM +0000, Sitaram Chamarty wrote:
> > We also plan to do it in this way, just a small wondering that it
> > looks a kind of workaround instead of a more graceful solution.
>
> I wouldn't consider it a workaround. It uses normal Unix
> permissions the way they were designed to, including setgid
> for directories.
Yes, I think core.sharedrepository is the "official" way to do this, so
it is definitely not a workaround.
> Actually, I am yet to come up with a situation where I
> actually needed ACLs, though they are more generalised, and
> fine-grained.
I like ACLs mainly because you don't have to bug root to change
permissions (like you do to get them to create or modify a group).
-Peff
next prev parent reply other threads:[~2009-01-07 6:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 7:00 Error: unable to unlink ... when using "git gc" Johnny Lee
2009-01-06 7:22 ` Jeff King
[not found] ` <488807870901052352w585da727r6d4a1e4ca4238cab@mail.gmail.com>
2009-01-06 8:03 ` Jeff King
2009-01-06 8:09 ` Johnny Lee
2009-01-06 11:57 ` Sitaram Chamarty
2009-01-06 15:05 ` Johnny Lee
2009-01-06 15:33 ` Sitaram Chamarty
2009-01-07 5:59 ` Jeff King [this message]
2009-01-07 6:27 ` Boyd Stephen Smith Jr.
2009-01-07 10:55 ` Sitaram Chamarty
2009-01-07 12:29 ` Sitaram Chamarty
2009-01-07 15:48 ` Boyd Stephen Smith Jr.
2009-01-07 18:00 ` Sitaram Chamarty
2009-01-07 19:46 ` Boyd Stephen Smith Jr.
2009-01-06 8:59 ` Junio C Hamano
2009-01-06 9:18 ` Johnny Lee
2009-01-06 13:27 ` Matthieu Moy
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=20090107055947.GA22616@coredump.intra.peff.net \
--to=peff@peff.net \
--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).