git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Johnny Lee" <johnnylee194@gmail.com>
To: "Sitaram Chamarty" <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Error: unable to unlink ... when using "git gc"
Date: Tue, 6 Jan 2009 23:05:17 +0800	[thread overview]
Message-ID: <488807870901060705m49419ec1he14aace5caaa3d89@mail.gmail.com> (raw)
In-Reply-To: <slrngm6hoj.n4a.sitaramc@sitaramc.homelinux.net>

Copy that.

Thanks Sitaram.

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.

Regards,
Johnny

On Tue, Jan 6, 2009 at 7:57 PM, Sitaram Chamarty <sitaramc@gmail.com> wrote:
> On 2009-01-06, Jeff King <peff@peff.net> wrote:
>> If you are going to have multiple users sharing a repository, generally
>> they should be in the same group and the core.sharedrepository config
>> option should be set (see "git help config", or the "shared" option to
>> git-init).
>>
>> I've never used that personally, though. I have always just used POSIX
>> ACLs, with a default ACL on each directory giving access to everyone.
>> E.g. (off the top of my head):
>>
>>   for user in user1 user2 user3; do
>>     setfacl -R -m u:$user:rwX -m d:u:$user:rwX /path/to/repo
>>   done
>
> If you're not worried about the finer-grained access control
> that acl(5) gives you, just do what "git init
> --shared=group" does:
>
>    git config core.sharedrepository 1 # as mentioned above
>    chmod g+ws .git
>
> Now set the group to something (I use "gitpushers" ;-)
>
>    chgrp -R gitpushers .git
>
> amd make sure all your users are part of that group.
>
> Works fine for small teams...
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
we all have our crosses to bear

  reply	other threads:[~2009-01-06 15:06 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 [this message]
2009-01-06 15:33           ` Sitaram Chamarty
2009-01-07  5:59             ` Jeff King
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=488807870901060705m49419ec1he14aace5caaa3d89@mail.gmail.com \
    --to=johnnylee194@gmail.com \
    --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).