git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nigel Magnay" <nigel.magnay@gmail.com>
To: "Logan Kennelly" <logank@sent.com>
Cc: "Robert Haines" <rhaines@manchester.ac.uk>, git <git@vger.kernel.org>
Subject: Re: permissions and packed-refs?
Date: Thu, 10 Apr 2008 20:21:38 +0100	[thread overview]
Message-ID: <320075ff0804101221n376e0c8mf9114f25dea6b2af@mail.gmail.com> (raw)
In-Reply-To: <135BAC69-9549-4E61-BD6F-A99364C27CCC@sent.com>

Yeah, I think that's probably what's happening. TBH it's a bit of an
ache to have to make sure umasks and things are set correctly, and
it's probably partially that the repo was set up just from a direct
copy of someone's machine.

We've reverted to using a common account user for now.

On Thu, Apr 10, 2008 at 7:19 PM, Logan Kennelly <logank@sent.com> wrote:
> On Apr 10, 2008, at 9:21 AM, Robert Haines wrote:
>
>
> > I've seen this after git gc too. Has the owner of the affected files
> changed? If so you need to make sure that git gc is run by the correct user.
> If you run it as root for example, everything it touches will end up owned
> by root!
> >
>
>  Not only that, but you must make sure that you have the appropriate umask
> set. I'm not sure if this affects the pack file, but the reflog is certainly
> rewritten in a way that prevents other users from pushing.
>
>  I've been meaning to submit a patch to make git better honor
> "core.sharedrepository" (it's probably as simple as adding a couple calls to
> adjust_shared_perm), but the workaround was so easy that I had forgotten
> about the issue.
>
>  --
>                                                         Logan Kennelly
>       ,,,
>      (. .)
>  --ooO-(_)-Ooo--
>
>
>
>

      reply	other threads:[~2008-04-10 19:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 12:30 permissions and packed-refs? Nigel Magnay
2008-04-10 16:21 ` Robert Haines
2008-04-10 18:19   ` Logan Kennelly
2008-04-10 19:21     ` Nigel Magnay [this message]

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=320075ff0804101221n376e0c8mf9114f25dea6b2af@mail.gmail.com \
    --to=nigel.magnay@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=logank@sent.com \
    --cc=rhaines@manchester.ac.uk \
    /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).