git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Johnny Lee" <johnnylee194@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Error: unable to unlink ... when using "git gc"
Date: Tue, 6 Jan 2009 16:09:16 +0800	[thread overview]
Message-ID: <488807870901060009i2f9f8b3dnb6be4b416d3b1318@mail.gmail.com> (raw)
In-Reply-To: <20090106080300.GA10079@coredump.intra.peff.net>

Ooops, forgot to cc to the mailing list.

Thanks for your sharing Peff, I'm going to check these stuffs out and
get back with any findings.

Regards,
Johnny

On Tue, Jan 6, 2009 at 4:03 PM, Jeff King <peff@peff.net> wrote:
> [re-adding git@vger; please keep discussion on-list so everyone can
> benefit from the result]
>
> On Tue, Jan 06, 2009 at 03:52:12PM +0800, Johnny Lee wrote:
>
>> Thanks Peff, I've checked the permission of .git/objects/16, it's
>> created by another user and thus I have no permission to remove it.
>>
>> In fact, this is coming from a previous bad practice on setting up a
>> collaboration repository on a SSH server, here is what I've done so
>> far:
>> [...]
>> 7. Then the user "git" has changed mode for all the files under .git
>> to writable.
>>
>> 8. This time, user "johnny" can push successfully.
>
> 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
>
> -Peff
>



-- 
we all have our crosses to bear

  reply	other threads:[~2009-01-06  8:10 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 [this message]
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
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=488807870901060009i2f9f8b3dnb6be4b416d3b1318@mail.gmail.com \
    --to=johnnylee194@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).