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@xxxxxxxx> 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-- > > > > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
